Nova install playbook causes temporary inability to schedule to compute nodes
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack-Ansible |
Confirmed
|
High
|
Unassigned |
Bug Description
I noted the following when patching one of our production environments. This involved rebuilding the virtualenv.
/etc/nova/ is a symlink into the virtualenv which gets removed during https:/
This is likely fine for files like nova.conf if these aren't dynamically re-read, but for 'vendor_data.json' which appears to be read when scheduling VMs to a compute node, this causes scheduling failures as follows:
Traceback (most recent call last): File "/openstack/
Whilst this issue is specific to Nova and the fix may be as simple as moving the dynamically read file into /var/lib/nova/, it perhaps indicates a wider issue for files in /etc/<service name>/ which may be dynamically read (perhaps policy files and similar) and exist for services which are targeted via RPC and not protected by HAProxy maintenance mode.
Yeah, ok, I think we've faced some issue in Neutron, but it was fixed there a while back with: /review. opendev. org/c/openstack /openstack- ansible- os_neutron/ +/788501
https:/
I didn't iterate over services back then as was not sure if anything else is affected in the same way. But apparently it is...