yahoo-eng-team team mailing list archive

[Chet Burgess <1575897@xxxxxxxxxxxxxxxxxx>]

Turns out this is already fixed earlier.

** Changed in: nova
       Status: New => Invalid

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

Title:
  evacuate breaks with config drive

Status in OpenStack Compute (nova):
  Invalid

Bug description:
  The config drive currently is only generated on initial boot. As a
  result of this if you have an instance that is a BFV instance and the
  hypervisor hosting the instance goes down you cannot issue an evacuate
  command on the instance because compute on the new destination will
  not re-generate the config drive but it will generate XML for libvirt
  that references the disk.config file. As a result the instance will go
  into an error state on the new destination.

  The config drive is not regenerated because the config drive can store
  the admin password as passed at boot. Since admin password is not
  persisted to the DB for security reason it can't be rebuilt.

  The best way to address this to to simply regenerate the config drive
  without the admin password. We should update the logic around evacuate
  to regenerate the config drive without the password so that the
  instance is at least still bootable.

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