yahoo-eng-team team mailing list archive

[wuhao <wuhao@xxxxxxxxxxxxxxx>]

Public bug reported:

We found this problem in Juno. But I think that may be reproduced in
each version.

Currently, _hard_reboot will regenerate instance config file, which
changes device bus addresses when the instance has hot plug-in devices,
like attach interfaces or volumes. If the address changes, then windows
will treat it as a new device.Unfortunately, power_on operation and
reboot operations in some cases will call the _hard_reboot function,
which is not what we expected.

Reproduce steps:
* create a window instance.
* create a new nic.
* shut down the instance and then reboot it.

Windows will find a new nic device.

** 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/1520319

Title:
  _hard_reboot func changes device bus addresses

Status in OpenStack Compute (nova):
  New

Bug description:
  We found this problem in Juno. But I think that may be reproduced in
  each version.

  Currently, _hard_reboot will regenerate instance config file, which
  changes device bus addresses when the instance has hot plug-in
  devices, like attach interfaces or volumes. If the address changes,
  then windows will treat it as a new device.Unfortunately, power_on
  operation and reboot operations in some cases will call the
  _hard_reboot function,  which is not what we expected.

  Reproduce steps:
  * create a window instance.
  * create a new nic.
  * shut down the instance and then reboot it.

  Windows will find a new nic device.

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