Comment 1 for bug 1430616

Revision history for this message
Eric Xie (mark-xiett) wrote :

I use Juno version, 2014.2.
Check the status of nova-compute service after stop ironic-api service, and get it:
# systemctl status openstack-nova-compute.service
openstack-nova-compute.service - OpenStack Nova Compute Server
   Loaded: loaded (/usr/lib/systemd/system/openstack-nova-compute.service; enabled)
   Active: active (running) since Wed 2015-03-11 12:01:22 CST; 1h 41min ago
 Main PID: 28778 (nova-compute)
   CGroup: /system.slice/openstack-nova-compute.service
           └─28778 /usr/bin/python /usr/bin/nova-compute

Mar 11 12:01:22 controller systemd[1]: Started OpenStack Nova Compute Server.

But in the log file of nova-compute:
2015-03-11 13:40:56.502 28778 TRACE nova.openstack.common.periodic_task NovaException: Error contacting Ironic server for 'node.list'. Attempt 60 of 60

Then start ironic-api service, and the exception was gone.

IMHO this flow does not process properly. When ironic-api service stopped, nova-compute service should be exited. But now it was running. End-user can launch one instance because 'nova-compute' service is up.