diff options
author | Matt Riedemann <mriedem.os@gmail.com> | 2017-10-27 16:03:15 -0400 |
---|---|---|
committer | Matt Riedemann <mriedem.os@gmail.com> | 2017-11-14 10:08:18 -0500 |
commit | 984dd8ad6add4523d93c7ce5a666a32233e02e34 (patch) | |
tree | 561e1f360c053b629a2e6f770d4ff8b2a09f45ed /releasenotes/notes/bug-1664931-validate-image-rebuild-9c5b05a001c94a4d.yaml | |
parent | 50c23d8c86f238665726b02c846c57ca92b86893 (diff) | |
download | nova-984dd8ad6add4523d93c7ce5a666a32233e02e34.tar.gz |
Validate new image via scheduler during rebuild
During a rebuild we bypass the scheduler because we are
always rebuilding the instance on the same host it's already
on. However, we allow passing a new image during rebuild
and that new image needs to be validated to work with the
instance host by running it through the scheduler filters,
like the ImagePropertiesFilter. Otherwise the new image
could violate constraints placed on the host by the admin.
This change checks to see if there is a new image provided
and if so, modifies the request spec passed to the scheduler
so that the new image is validated all while restricting
the scheduler to still pick the same host that the instance
is running on. If the image is not valid for the host, the
scheduler will raise NoValidHost and the rebuild stops.
A functional test is added to show the recreate of the bug
and that we probably stop the rebuild now in conductor by
calling the scheduler to validate the image.
Co-Authored-By: Sylvain Bauza <sbauza@redhat.com>
Closes-Bug: #1664931
Change-Id: I11746d1ea996a0f18b7c54b4c9c21df58cc4714b
Diffstat (limited to 'releasenotes/notes/bug-1664931-validate-image-rebuild-9c5b05a001c94a4d.yaml')
0 files changed, 0 insertions, 0 deletions