Mark Goddard 192dcd1e1b Fix booting instances after nova-compute upgrade
After upgrading from Rocky to Stein, nova-compute services fail to start
new instances with the following error message:

Failed to allocate the network(s), not rescheduling.

Looking in the nova-compute logs, we also see this:

Neutron Reported failure on event
network-vif-plugged-60c05a0d-8758-44c9-81e4-754551567be5 for instance
32c493c4-d88c-4f14-98db-c7af64bf3324: NovaException: In shutdown, no new
events can be scheduled

During the upgrade process, we send nova containers a SIGHUP to cause
them to reload their object version state. Speaking to the nova team in
IRC, there is a known issue with this, caused by oslo.service performing
a full shutdown in response to a SIGHUP, which breaks nova-compute.
There is a patch [1] in review to address this.

The workaround employed here is to restart the nova compute service.

[1] https://review.openstack.org/#/c/641907

Change-Id: Ia4fcc558a3f62ced2d629d7a22d0bc1eb6b879f1
Closes-Bug: #1821362
2019-03-22 16:26:36 +00:00
..
2018-11-26 08:07:01 +00:00
2018-11-26 08:07:01 +00:00
2018-11-26 08:07:01 +00:00
2019-02-25 19:30:33 +01:00
2018-11-26 08:07:01 +00:00
2018-11-26 08:07:01 +00:00
2018-11-26 08:07:01 +00:00
2019-03-01 14:36:25 +00:00
2019-02-19 11:13:08 +00:00
2019-03-11 18:26:12 +00:00
2018-11-26 08:07:01 +00:00
2019-03-21 12:31:23 +00:00
2018-12-05 11:44:37 +00:00
2018-11-26 08:07:01 +00:00
2019-03-15 15:19:54 +00:00
2018-11-26 08:07:01 +00:00
2018-11-26 08:07:01 +00:00
2018-11-26 08:07:01 +00:00
2018-11-26 08:07:01 +00:00
2019-03-07 15:50:41 +01:00
2019-03-06 15:08:26 -05:00