This change reorders the call in
_update_instance_after_spawn so that we call
configdrive.update_instance before we set
instance.launched_at. This ensures that if the vm
is booted with a config drive because the host had
force_config_drive=true the instance will keep its
config drive across reboots.
This change fixes a regression introduced as part
of fixing bug #1827492 which addressed failing
to boot vms after changing force_config_drive=false
to force_config_drive=true.
Reviewed: https:/ /review. opendev. org/669738 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=641feb62a33 e211a3ed1f9a230 9ee16d827f5fe2
Committed: https:/
Submitter: Zuul
Branch: master
commit 641feb62a33e211 a3ed1f9a2309ee1 6d827f5fe2
Author: Sean Mooney <email address hidden>
Date: Mon Jul 8 18:35:11 2019 +0000
make config drives sticky bug 1835822
This change reorders the call in instance_ after_spawn so that we call .update_ instance before we set launched_ at. This ensures that if the vm config_ drive=true the instance will keep its
_update_
configdrive
instance.
is booted with a config drive because the host had
force_
config drive across reboots.
This change fixes a regression introduced as part drive=false drive=true.
of fixing bug #1827492 which addressed failing
to boot vms after changing force_config_
to force_config_
Change-Id: I9194423f5f95e9 799bd891548e247 56131d65e76
Related-Bug: #1827492
Closes-Bug: #1835822