rebooting a centos compute node loses /var/lock/nova
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack-Ansible |
Confirmed
|
Undecided
|
Unassigned | ||
Bug Description
On centos 7 and later /var/lock is tmpfs symlinked to /run, so the nova lock directory is missing once a node is rebooted after deployment.
We had a user report this in #openstack-ansible for the stein release on centos7
10:43 AM <key-networks> G'day folks. Just wondering if you do any reboot tests in your CI testing? On Friday I deployed stein AIO on CentOS 7. It worked fine until I rebooted the host and restarted galera cluster - nova-compute was dead. The nova-compute log said Permission denied: '/var/lock/nova' - the directory did not exist, so I followed https:/
10:43 AM <key-networks> essfully. After another reboot, I checked that nova-compute was running before restarting galera cluster. After restarting galera, nova-compute died and /var/lock/nova disappeared again. I then scrapped CentOS 7, installed Ubuntu 18.04 and have had a lot more success since then.
10:43 AM <@openstack> Launchpad bug 1636604 in openstack-ansible "Nova fails to launch any instances after the compute host is rebooted" [Undecided,Fix released] - Assigned to Paulo Matias (paulo-matias)
| Chris Smart (csmart) wrote | #1 |
| Chris Smart (csmart) wrote | #2 |
| Changed in openstack-ansible: | |
| status: | New → Confirmed |
Creating the following file should work around it for now:
cat << EOF | sudo tee /usr/lib/
D /var/lock/nova 2770 root nova
EOF
This tells systemd to create that tmpfile (everything is under /run now) on boot.