Comment 19 for bug 1543951

Got the same issue on baremetal lab, 2 of 3 computes were offline after cluster reboot. Libvirt daemon was started after Nova compute:

root@node-6:~# grep -E -i 'libvirt|compute' /var/log/boot.log
 * Starting OpenStack Compute [ OK ]
 * Starting libvirt management daemon libvirtd [ OK ]

root@node-6:~# ps aux | grep libvirt
root 4689 0.0 0.0 748964 10688 ? Sl 18:35 0:00 /usr/sbin/libvirtd -d -d -l
root 44068 0.0 0.0 10460 940 pts/0 R+ 22:38 0:00 grep --color=auto libvirt
root@node-6:~# ps aux | grep nova
nova 3968 0.0 0.7 1919088 116496 ? Ssl 18:35 0:03 /usr/bin/python /usr/bin/nova-compute --config-file=/etc/nova/nova.conf --config-file=/etc/nova/nova-compute.conf --log-file=/var/log/nova/nova-compute.log
root 44129 0.0 0.0 10464 932 pts/0 S+ 22:39 0:00 grep --color=auto nova

root@node-6:~# stat /proc/4689/cmdline
  File: ‘/proc/4689/cmdline’
  Size: 0 Blocks: 0 IO Block: 1024 regular empty file
Device: 3h/3d Inode: 21603 Links: 1
Access: (0444/-r--r--r--) Uid: ( 0/ root) Gid: ( 0/ root)
Access: 2016-02-10 18:35:32.997506503 +0000
Modify: 2016-02-10 18:35:32.997506503 +0000
Change: 2016-02-10 18:35:32.997506503 +0000
 Birth: -
root@node-6:~# stat /proc/3968/cmdline
  File: ‘/proc/3968/cmdline’
  Size: 0 Blocks: 0 IO Block: 1024 regular empty file
Device: 3h/3d Inode: 19716 Links: 1
Access: (0444/-r--r--r--) Uid: ( 107/ nova) Gid: ( 114/ nova)
Access: 2016-02-10 18:35:26.158112335 +0000
Modify: 2016-02-10 18:35:26.158112335 +0000
Change: 2016-02-10 18:35:26.158112335 +0000
 Birth: -

I also think that the bug is caused by missconfiguration of 'libvirt-daemon-system' package, currently 'libritd' daemon is not managed by upstart:

root@node-6:~# initctl list | grep -i -E 'libvirt|compute'
nova-compute start/running, process 3968

root@node-6:~# service --status-all 2>&1| grep -i -E 'libvirt|compute'
 [ + ] libvirt-guests
 [ + ] libvirtd
 [ + ] nova-compute

So 'Should-Start' with 'libvirt' boot_facility in Nova compute init script makes no sense now.