| 2017-04-19 14:32:18 |
james beedy |
bug |
|
|
added bug |
| 2017-04-19 14:33:36 |
james beedy |
description |
juju deployed lxd is failing across the board for me right now on aws instances.
I created a new model this morning (first model I've created on 2.1.2), and went to deploy some charms, and my lxd status just shows "down": http://paste.ubuntu.com/24413976/
I initially thought it might be a 2.1.2 thing, so I verified a one of my older 2.0.3 models.
You can see here (2.0.3) http://paste.ubuntu.com/24414148/, this use case was working for me, and then machine 10 which was deployed this morning exhibits the bug. |
juju deployed lxd is failing across the board for me right now on aws instances using the JAAS controller.
I created a new model this morning (first model I've created on 2.1.2), and went to deploy some charms, and my lxd status just shows "down": http://paste.ubuntu.com/24413976/
I initially thought it might be a 2.1.2 thing, so I verified a one of my older 2.0.3 models.
You can see here (2.0.3) http://paste.ubuntu.com/24414148/, this use case was working for me, and then machine 10 which was deployed this morning exhibits the bug. |
|
| 2017-04-19 14:46:30 |
james beedy |
description |
juju deployed lxd is failing across the board for me right now on aws instances using the JAAS controller.
I created a new model this morning (first model I've created on 2.1.2), and went to deploy some charms, and my lxd status just shows "down": http://paste.ubuntu.com/24413976/
I initially thought it might be a 2.1.2 thing, so I verified a one of my older 2.0.3 models.
You can see here (2.0.3) http://paste.ubuntu.com/24414148/, this use case was working for me, and then machine 10 which was deployed this morning exhibits the bug. |
juju deployed lxd is failing across the board for me right now on aws instances using the JAAS controller.
I created a new model this morning (first model I've created on 2.1.2), and went to deploy some charms, and my lxd status just shows "down": http://paste.ubuntu.com/24413976/
I initially thought it might be a 2.1.2 thing, so I verified a one of my older 2.0.3 models.
You can see here (2.0.3) http://paste.ubuntu.com/24414148/, this use case was working for me, and then machine 10 which was deployed this morning exhibits the bug.
To reproduce this:
1) deploy an instance to aws `juju add-machine`
2) deploy something to lxd on the newly created machine `juju deploy redis --to lxd:#` |
|
| 2017-04-19 14:49:14 |
james beedy |
description |
juju deployed lxd is failing across the board for me right now on aws instances using the JAAS controller.
I created a new model this morning (first model I've created on 2.1.2), and went to deploy some charms, and my lxd status just shows "down": http://paste.ubuntu.com/24413976/
I initially thought it might be a 2.1.2 thing, so I verified a one of my older 2.0.3 models.
You can see here (2.0.3) http://paste.ubuntu.com/24414148/, this use case was working for me, and then machine 10 which was deployed this morning exhibits the bug.
To reproduce this:
1) deploy an instance to aws `juju add-machine`
2) deploy something to lxd on the newly created machine `juju deploy redis --to lxd:#` |
juju deployed lxd is failing across the board for me right now on aws instances using the JAAS controller.
I created a new model this morning (first model I've created on 2.1.2), and went to deploy some charms, and my lxd status just shows "down": http://paste.ubuntu.com/24413976/
I initially thought it might be a 2.1.2 thing, so I verified a one of my older 2.0.3 models.
You can see here (2.0.3) http://paste.ubuntu.com/24414148/, this use case was working for me, and then machine 10 which was deployed this morning exhibits the bug.
To reproduce:
1) deploy an instance to aws `juju add-machine`
2) deploy something to lxd on the newly created machine `juju deploy redis --to lxd:#` |
|
| 2017-04-20 01:12:44 |
Menno Finlay-Smits |
juju: status |
New |
Triaged |
|
| 2017-04-20 01:13:38 |
Menno Finlay-Smits |
juju: importance |
Undecided |
High |
|
| 2017-04-20 01:13:40 |
Menno Finlay-Smits |
juju: milestone |
|
2.2.0 |
|
| 2017-04-20 01:29:28 |
Anastasia |
juju: milestone |
2.2.0 |
2.2-rc1 |
|
| 2017-04-20 14:27:59 |
John A Meinel |
juju: status |
Triaged |
Incomplete |
|
| 2017-04-20 14:44:34 |
Anastasia |
juju: importance |
High |
Undecided |
|
| 2017-04-20 14:44:36 |
Anastasia |
juju: milestone |
2.2-rc1 |
|
|
| 2017-04-20 22:09:15 |
Anastasia |
juju: status |
Incomplete |
New |
|
| 2017-04-26 00:56:16 |
Tim Penhey |
tags |
|
intermittent-failure |
|
| 2017-05-09 16:19:30 |
John A Meinel |
juju: status |
New |
Triaged |
|
| 2017-05-09 16:19:33 |
John A Meinel |
juju: status |
Triaged |
In Progress |
|
| 2017-05-09 16:19:34 |
John A Meinel |
juju: importance |
Undecided |
Critical |
|
| 2017-05-09 16:19:38 |
John A Meinel |
juju: assignee |
|
John A Meinel (jameinel) |
|
| 2017-05-09 16:19:42 |
John A Meinel |
juju: milestone |
|
2.2-beta4 |
|
| 2017-05-11 18:21:41 |
Canonical Juju QA Bot |
juju: milestone |
2.2-beta4 |
2.2-rc1 |
|
| 2017-06-01 04:04:35 |
John A Meinel |
marked as duplicate |
|
1685782 |
|
