Public bug reported:
As of stable/pike if we do a rebuild-to-same-node with a new image, it
results in ComputeManager.rebuild_instance() being called with
"scheduled_node=<hostname>" and "recreate=False". This results in a new
Claim, which seems wrong since we're not changing the flavor and that
claim could fail if the compute node is already full.
The comments in ComputeManager.rebuild_instance() make it appear that it
expects both "recreate" and "scheduled_node" to be None for the rebuild-
to-same-host case otherwise it will do a Claim. However, if we rebuild
to a different image it ends up going through the scheduler which means
that "scheduled_node" is not None.
** Affects: nova
Importance: Undecided
Status: New
** Tags: compute rebuild
--
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/1750618
Title:
rebuild to same host with a different image results in erroneously
doing a Claim
Status in OpenStack Compute (nova):
New
Bug description:
As of stable/pike if we do a rebuild-to-same-node with a new image, it
results in ComputeManager.rebuild_instance() being called with
"scheduled_node=<hostname>" and "recreate=False". This results in a
new Claim, which seems wrong since we're not changing the flavor and
that claim could fail if the compute node is already full.
The comments in ComputeManager.rebuild_instance() make it appear that
it expects both "recreate" and "scheduled_node" to be None for the
rebuild-to-same-host case otherwise it will do a Claim. However, if
we rebuild to a different image it ends up going through the scheduler
which means that "scheduled_node" is not None.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1750618/+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
