** Also affects: tripleo
Importance: Undecided
Status: New
** Changed in: tripleo
Status: New => In Progress
** Changed in: tripleo
Importance: Undecided => Critical
** Changed in: tripleo
Milestone: None => stein-1
** Changed in: tripleo
Assignee: (unassigned) => Bogdan Dobrelya (bogdando)
--
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 prenvents instances to boot
Status in OpenStack Compute (nova):
Confirmed
Status in tripleo:
In Progress
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
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
