nova-compute does not start at boot due to unsatisfied libvirt-bin dependency

Bug #1043864 reported by Elvinas Piliponis on 2012-08-30
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nova (Ubuntu)

Bug Description

-- nova-compute service fails to start automatically at boot due to race condition and as a result unsatisfied service dependency libvirt-bin service.
-- Nova-compute log files shows that no libvirt socket was available at start time:
tail -n 3 /var/log/nova/nova-compute.log
2012-08-30 14:23:24 TRACE nova if ret is None:raise libvirtError('virConnectOpenAuth() failed')
2012-08-30 14:23:24 TRACE nova libvirtError: Failed to connect socket to '/var/run/libvirt/libvirt-sock': No such file or directory
2012-08-30 14:23:24 TRACE nova
-- However libvirt is stated at the boot:
service libvirt-bin status
libvirt-bin start/running, process 2971
-- nova compute ca be succesfully started manually
service nova-compute start
nova-compute start/running, process 3714
service nova-compute status
nova-compute start/running, process 3714
tail -n 3 /var/log/nova/nova-compute.log
2012-08-30 15:09:27 INFO nova.virt.libvirt.connection [-] Compute_service record created for COMPUTE-NODE
2012-08-30 15:09:27 INFO nova.rpc.common [-] Connected to AMQP server on REGION-CONTROLLER:5672
2012-08-30 15:09:27 DEBUG nova.service [-] Creating Consumer connection for Service compute from (pid=3715) start /usr/lib/python2.7/dist-packages/nova/

-- version
dpkg -l | grep nova-compute
ii nova-compute 2012.1+stable~20120612-3ee026e-0ubuntu1.2 OpenStack Compute - compute node
lsb_release -rd
Description: Ubuntu 12.04.1 LTS
Release: 12.04

How reproducible: Always. Restart compute node and check nova-compute service.

Suggested fix: Add libvirt-bin service dependency to nova-compute service in /etc/init/nova-compute.conf file
Replace this:
start on (filesystem and net-device-up IFACE!=lo)
stop on runlevel [016]
with this:
start on (filesystem and net-device-up IFACE!=lo)
start on started libvirt-bin
stop on runlevel [016]

Package name corrected.

Possibly a duplicate of teh following issue although binary packages are different:

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers