yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #80227
[Bug 1715374] Re: Reloading compute with SIGHUP prevents instances from booting
as of https://github.com/openstack/nova/commit/73f1fda7e93325d3ca2b2c62afb17fe011d650f3
this is now fix in nova 20.0.0.0rc1
the osls.service issue was fixed in release 1.40.1
** Changed in: nova
Status: In Progress => Fix Released
** Changed in: oslo.service
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1715374
Title:
Reloading compute with SIGHUP prevents instances from booting
Status in OpenStack Compute (nova):
Fix Released
Status in openstack-ansible:
Confirmed
Status in oslo.service:
Fix Released
Status in tripleo:
Won't Fix
Bug description:
When trying to boot a new instance at a compute-node, where nova-
compute received SIGHUP(the SIGHUP is used as a trigger for reloading
mutable options), it always failed.
========== nova/compute/manager.py ==============
def cancel_all_events(self):
if self._events is None:
LOG.debug('Unexpected attempt to cancel events during shutdown.')
return
our_events = self._events
# NOTE(danms): Block new events
self._events = None <--- Set self._events to "None"
...
=================================================
This will cause a NovaException when prepare_for_instance_event() was called.
It's the cause of the failure of network allocation.
========== nova/compute/manager.py ==============
def prepare_for_instance_event(self, instance, event_name):
...
if self._events is None:
# NOTE(danms): We really should have a more specific error
# here, but this is what we use for our default error case
raise exception.NovaException('In shutdown, no new events '
'can be scheduled')
=================================================
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1715374/+subscriptions
References