yahoo-eng-team team mailing list archive

["Kyle L. Henderson" <kyleh@xxxxxxxxxx>]

Public bug reported:

I'm working on the nova-powervm driver for Mitaka and trying to add
support for evacuation.

The problem I'm hitting is that instance.host is not updated when the
compute driver is called to spawn the instance on the destination host.
It is still set to the source host.  It's not until after the spawn
completes that the compute manager updates instance.host to reflect the
destination host.

The nova-powervm driver uses instance events callback mechanism during
plug VIF to determine when Neutron has finished provisioning the
network.  The instance events code sends the event to instance.host and
hence is sending the event to the source host (which is down).  This
causes the spawn to fail and also causes weirdness when the source host
gets the events when it's powered back up.

To temporarily work around the problem, I hacked in setting
instance.host = CONF.host; instance.save() in the compute driver but
that's not a good solution.

** Affects: nova
     Importance: Undecided
         Status: New

-- 
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/1535918

Title:
  instance.host not updated on evacuation

Status in OpenStack Compute (nova):
  New

Bug description:
  I'm working on the nova-powervm driver for Mitaka and trying to add
  support for evacuation.

  The problem I'm hitting is that instance.host is not updated when the
  compute driver is called to spawn the instance on the destination
  host.  It is still set to the source host.  It's not until after the
  spawn completes that the compute manager updates instance.host to
  reflect the destination host.

  The nova-powervm driver uses instance events callback mechanism during
  plug VIF to determine when Neutron has finished provisioning the
  network.  The instance events code sends the event to instance.host
  and hence is sending the event to the source host (which is down).
  This causes the spawn to fail and also causes weirdness when the
  source host gets the events when it's powered back up.

  To temporarily work around the problem, I hacked in setting
  instance.host = CONF.host; instance.save() in the compute driver but
  that's not a good solution.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1535918/+subscriptions