Launching an instance error out Exception during scheduler.run_instance
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R2.20 |
Fix Committed
|
Critical
|
Sanju Abraham | |||
Trunk |
Fix Committed
|
Critical
|
Sanju Abraham |
Bug Description
On a 2.20 46 Juno based HA install patched with oslo patches, launching instances errors out
The below traceback is seen in the nova conductor log
root@cs-
15-06-10 20:31:43.789 2479 INFO oslo.messaging.
2015-06-10 20:32:42.757 2479 ERROR nova.scheduler.
2015-06-10 20:32:42.757 2479 TRACE nova.scheduler.
2015-06-10 20:32:42.757 2479 TRACE nova.scheduler.
2015-06-10 20:32:42.757 2479 TRACE nova.scheduler.
2015-06-10 20:32:42.757 2479 TRACE nova.scheduler.
2015-06-10 20:32:42.757 2479 TRACE nova.scheduler.
2015-06-10 20:32:42.757 2479 TRACE nova.scheduler.
2015-06-10 20:32:42.757 2479 TRACE nova.scheduler.
2015-06-10 20:32:42.757 2479 TRACE nova.scheduler.
2015-06-10 20:32:42.757 2479 TRACE nova.scheduler.
2015-06-10 20:32:42.757 2479 TRACE nova.scheduler.
2015-06-10 20:32:42.757 2479 TRACE nova.scheduler.
2015-06-10 20:32:42.757 2479 TRACE nova.scheduler.
2015-06-10 20:32:42.757 2479 TRACE nova.scheduler.
2015-06-10 20:32:42.757 2479 TRACE nova.scheduler.
2015-06-10 20:32:42.757 2479 TRACE nova.scheduler.
2015-06-10 20:32:42.757 2479 TRACE nova.scheduler.
2015-06-10 20:32:42.757 2479 TRACE nova.scheduler.
2015-06-10 20:32:42.757 2479 TRACE nova.scheduler.
2015-06-10 20:32:42.757 2479 TRACE nova.scheduler.
2015-06-10 20:32:42.757 2479 TRACE nova.scheduler.
2015-06-10 20:32:42.757 2479 TRACE nova.scheduler.
2015-06-10 20:32:42.757 2479 TRACE nova.scheduler.
2015-06-10 20:32:42.757 2479 TRACE nova.scheduler.
2015-06-10 20:32:42.757 2479 TRACE nova.scheduler.
2015-06-10 20:32:42.757 2479 TRACE nova.scheduler.
2015-06-10 20:32:42.757 2479 TRACE nova.scheduler.
2015-06-10 20:32:42.757 2479 TRACE nova.scheduler.
2015-06-10 20:32:42.761 2479 WARNING nova.scheduler.
rabbitmq cluster is ok, so is nova services
root@cs-
Cluster status of node 'rabbit@
[{nodes,
{running_
{cluster_
{partitions,[]}]
root@cs-
+----+-
| Id | Binary | Host | Zone | Status | State | Updated_at | Disabled Reason |
+----+-
| 3 | nova-scheduler | cs-scale-1 | internal | enabled | up | 2015-06-
| 6 | nova-console | cs-scale-1 | internal | enabled | up | 2015-06-
| 9 | nova-consoleauth | cs-scale-1 | internal | enabled | up | 2015-06-
| 12 | nova-conductor | cs-scale-1 | internal | enabled | up | 2015-06-
| 15 | nova-scheduler | cs-scale-2 | internal | enabled | up | 2015-06-
| 18 | nova-console | cs-scale-2 | internal | enabled | up | 2015-06-
| 21 | nova-consoleauth | cs-scale-2 | internal | enabled | up | 2015-06-
| 24 | nova-conductor | cs-scale-2 | internal | enabled | up | 2015-06-
| 27 | nova-scheduler | cs-scale-3 | internal | enabled | up | 2015-06-
| 30 | nova-console | cs-scale-3 | internal | enabled | up | 2015-06-
| 33 | nova-consoleauth | cs-scale-3 | internal | enabled | up | 2015-06-
| 36 | nova-conductor | cs-scale-3 | internal | enabled | up | 2015-06-
| 42 | nova-compute | cs-scale-4 | nova | enabled | up | 2015-06-
| 45 | nova-compute | cs-scale-5 | nova | enabled | up | 2015-06-
| 48 | nova-compute | cs-scale-6 | nova | enabled | up | 2015-06-
| 51 | nova-compute | cs-scale-7 | nova | enabled | up | 2015-06-
| 54 | nova-compute | cs-scale-8 | nova | enabled | up | 2015-06-
+----+-
root@cs-
There are 3 openstack controllers in the setup.
1- 10.87.141.1
2- 10.87.141.2
3- 10.87.141.3
On 1 - nova conductor was restarted after the olso messaging changes were applied..
nova 5361 2046 1 00:23 ? 00:15:32 /usr/bin/python /usr/bin/ nova-conductor --config- file=/etc/ nova/nova. conf
On 2 - nova conductor was not restart
nova 2331 19293 1 Jun09 ? 00:20:35 /usr/bin/python /usr/bin/ nova-conductor --config- file=/etc/ nova/nova. conf
On 3 - nova conductor was restarted.
nova 3510 2701 0 00:24 ? 00:02:01 /usr/bin/python /usr/bin/ nova-conductor --config- file=/etc/ nova/nova. conf ======= ======= ======= ======= ======
=======
The reason why there is the traceback in the log from the 2nd node is because the patch application procedure was not complete.
Please restart nova-conductor and it should be OK.