Mitaka ironic-conductor error on stop: Cannot switch to MAINLOOP from MAINLOOP
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ironic |
Expired
|
Undecided
|
Unassigned | ||
Mitaka |
Expired
|
Undecided
|
Unassigned | ||
ironic (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
Using the mitaka packages from trusty/proposed:
ii ironic-api 1:5.1.0-
ii ironic-common 1:5.1.0-
ii ironic-conductor 1:5.1.0-
ii python-ironic 1:5.1.0-
ii python-ironic-lib 1.1.0-1~cloud0 all common library used by various Ironic projects - Python 2.7
ii python-ironicclient 1.2.0-0ubuntu1~
I'm not sure what's going on but conductor is throwing this when stopping:
However it is actually no longer running:
2016-04-05 04:27:42.089 8920 ERROR ironic.
2016-04-05 04:27:42.089 8920 ERROR ironic.
2016-04-05 04:27:42.089 8920 ERROR ironic.
2016-04-05 04:27:42.089 8920 ERROR ironic.
2016-04-05 04:27:42.089 8920 ERROR ironic.
2016-04-05 04:27:42.089 8920 ERROR ironic.
2016-04-05 04:27:42.089 8920 ERROR ironic.
2016-04-05 04:27:42.089 8920 ERROR ironic.
2016-04-05 04:27:42.089 8920 ERROR ironic.
2016-04-05 04:27:42.089 8920 ERROR ironic.
2016-04-05 04:27:42.089 8920 ERROR ironic.
2016-04-05 04:27:42.089 8920 ERROR ironic.
2016-04-05 04:27:42.089 8920 ERROR ironic.
2016-04-05 04:27:42.089 8920 ERROR ironic.
2016-04-05 04:27:42.089 8920 ERROR ironic.
2016-04-05 04:27:42.089 8920 ERROR ironic.
2016-04-05 04:27:42.089 8920 ERROR ironic.
2016-04-05 04:27:42.089 8920 ERROR ironic.
2016-04-05 04:27:42.089 8920 ERROR ironic.
2016-04-05 04:27:42.089 8920 ERROR ironic.
2016-04-05 04:27:42.089 8920 ERROR ironic.
2016-04-05 04:27:42.089 8920 ERROR ironic.
summary: |
- Mitaka ironic-conductor won't start: Cannot switch to MAINLOOP from + Mitaka ironic-conductor error on stop: Cannot switch to MAINLOOP from MAINLOOP |
Changed in ironic (Ubuntu): | |
status: | New → Won't Fix |
What version of Oslo.service are you running? http:// lists.openstack .org/pipermail/ openstack- dev/2016- February/ 086978. html appears to indicate it's a problem with an incompatible version of Oslo.service.
I've marked this bug "incomplete" pending that information, as until we know it we can't address your problem.
Thanks!