It's clear that we could have a RequestSpec.instance_group
without a uuid field if the InstanceGroup is set from the
_populate_group_info method which should only be used for
legacy translation of request specs using legacy filter
properties dicts.
To workaround the issue, we look for the group scheduler hint
to get the group uuid before loading it from the DB.
The related functional regression recreate test is updated
to show this solves the issue.
Reviewed: https:/ /review. opendev. org/661786 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=da453c2bfe8 6ab7a825f0aa7eb ced15886f7a5fd
Committed: https:/
Submitter: Zuul
Branch: master
commit da453c2bfe86ab7 a825f0aa7ebced1 5886f7a5fd
Author: Matt Riedemann <email address hidden>
Date: Tue May 28 11:24:11 2019 -0400
Workaround missing RequestSpec. instance_ group.uuid
It's clear that we could have a RequestSpec. instance_ group group_info method which should only be used for
without a uuid field if the InstanceGroup is set from the
_populate_
legacy translation of request specs using legacy filter
properties dicts.
To workaround the issue, we look for the group scheduler hint
to get the group uuid before loading it from the DB.
The related functional regression recreate test is updated
to show this solves the issue.
Change-Id: I20981c987549ee c40ad9762e74b0d b16e54f4e63
Closes-Bug: #1830747