| 2017-02-28 22:48:58 |
Jason Hobbs |
bug |
|
|
added bug |
| 2017-02-28 22:49:42 |
Jason Hobbs |
description |
I'm trying to kill a controller that shows up in my controllers list, but juju fails to do so:
http://paste.ubuntu.com/24086765/
This is with juju 2.1.
We rely on kill-controller always working and if it doesn't, it hangs up or automation. |
I'm trying to kill a controller that shows up in my controllers list, but juju fails to do so:
http://paste.ubuntu.com/24086765/
We rely on kill-controller always working and if it doesn't, it hangs up or automation.
This is with 1:2.1.0-0ubuntu1~16.04.1~juju1 |
|
| 2017-02-28 22:51:33 |
Jason Hobbs |
description |
I'm trying to kill a controller that shows up in my controllers list, but juju fails to do so:
http://paste.ubuntu.com/24086765/
We rely on kill-controller always working and if it doesn't, it hangs up or automation.
This is with 1:2.1.0-0ubuntu1~16.04.1~juju1 |
I'm trying to kill a controller that shows up in my controllers list, but juju fails to do so:
http://paste.ubuntu.com/24086765/
It's an OpenStack controller.
We rely on kill-controller always working and if it doesn't, it hangs up or automation.
Here is my controllers.yaml:
https://pastebin.canonical.com/180985/
This is with 1:2.1.0-0ubuntu1~16.04.1~juju1 |
|
| 2017-03-01 01:25:02 |
Anastasia |
juju: status |
New |
Incomplete |
|
| 2017-03-02 20:27:01 |
Jason Hobbs |
description |
I'm trying to kill a controller that shows up in my controllers list, but juju fails to do so:
http://paste.ubuntu.com/24086765/
It's an OpenStack controller.
We rely on kill-controller always working and if it doesn't, it hangs up or automation.
Here is my controllers.yaml:
https://pastebin.canonical.com/180985/
This is with 1:2.1.0-0ubuntu1~16.04.1~juju1 |
I'm trying to kill a controller that shows up in my controllers list, but juju fails to do so:
http://paste.ubuntu.com/24086765/
It's an OpenStack controller, and in this case, the machines that were running OpenStack are no longer around, so juju can't reach the controller or OpenStack at all. It's easy to reproduce by adding an openstack controller in your controllers.yaml that has IPs that can't be reached.
We rely on kill-controller always working and if it doesn't, it hangs up or automation.
Here is my controllers.yaml:
https://pastebin.canonical.com/180985/
This is with 1:2.1.0-0ubuntu1~16.04.1~juju1 |
|
| 2017-03-02 20:27:05 |
Jason Hobbs |
juju: status |
Incomplete |
New |
|
| 2017-03-02 20:27:29 |
Jason Hobbs |
summary |
kill-controller fails with "ERROR getting controller environ: unable to get bootstrap information from client store or API" |
kill-controller fails with "ERROR getting controller environ: unable to get bootstrap information from client store or API" when controller is no longer running (on OpenStack) |
|
| 2017-03-02 20:42:03 |
Jason Hobbs |
tags |
oil |
cdo-qa-blocker oil |
|
| 2017-03-02 22:12:59 |
Tim Penhey |
tags |
cdo-qa-blocker oil |
cdo-qa-blocker oil sprint |
|
| 2017-03-02 22:13:03 |
Tim Penhey |
juju: status |
New |
Triaged |
|
| 2017-03-02 22:13:06 |
Tim Penhey |
juju: importance |
Undecided |
Medium |
|
| 2017-03-02 22:51:29 |
Anastasia |
juju: milestone |
|
2.2-beta1 |
|
| 2017-03-02 22:53:41 |
Anastasia |
juju: importance |
Medium |
High |
|
| 2017-03-03 15:31:08 |
Jason Hobbs |
description |
I'm trying to kill a controller that shows up in my controllers list, but juju fails to do so:
http://paste.ubuntu.com/24086765/
It's an OpenStack controller, and in this case, the machines that were running OpenStack are no longer around, so juju can't reach the controller or OpenStack at all. It's easy to reproduce by adding an openstack controller in your controllers.yaml that has IPs that can't be reached.
We rely on kill-controller always working and if it doesn't, it hangs up or automation.
Here is my controllers.yaml:
https://pastebin.canonical.com/180985/
This is with 1:2.1.0-0ubuntu1~16.04.1~juju1 |
I'm trying to kill a controller that shows up in my controllers list, but juju fails to do so:
http://paste.ubuntu.com/24086765/
It's an OpenStack controller, and in this case, the machines that were running OpenStack are no longer around, so juju can't reach the controller or OpenStack at all. It's easy to reproduce by adding an openstack controller in your controllers.yaml that has IPs that can't be reached.
We rely on kill-controller always working and if it doesn't, it hangs up or automation.
Here is my controllers.yaml:
https://pastebin.canonical.com/180985/
This is with 2.1.0-0ubuntu1~16.04.1~juju1 |
|
| 2017-03-16 04:20:22 |
Anastasia |
juju: milestone |
2.2-alpha1 |
2.2-beta1 |
|
| 2017-03-21 05:02:27 |
Anastasia |
juju: milestone |
2.2-beta1 |
|
|
| 2017-03-21 23:25:09 |
Anastasia |
juju: status |
Triaged |
Incomplete |
|
| 2017-04-05 21:14:29 |
Jason Hobbs |
juju: status |
Incomplete |
Invalid |
|
