132636dd61
We don't support changing the image in the root disk of a volume-backed server during a rebuild. The API will change the instance.image_ref attribute to the newly supplied image_href to the rebuild API but the actual image used by the server after the rebuild will be the original image, which is wrong. We need to just fail fast in this case in the API since the compute service doesn't support it. We also need to ensure that instance.image_ref doesn't get modified since a missing value here is used by novaclient and probably other HTTP API users as an indication of a volume-backed server. See the related mailing list discussion for more details: http://lists.openstack.org/pipermail/openstack-dev/2017-October/123255.html Co-Authored-By: Chris Friesen <chris.friesen@windriver.com> Change-Id: If4c5fb782bb7e7714fb44f8ca9875121e066bc10 Closes-Bug: #1482040
12 lines
526 B
YAML
12 lines
526 B
YAML
---
|
|
fixes:
|
|
- |
|
|
A fix is made for `bug 1482040`_ where a request to rebuild a volume-backed
|
|
server with a new image which is different than what is in the root volume
|
|
will now fail with a `400 Bad Request` response. The compute API would
|
|
previously return a `202 Accepted` response but the backend compute service
|
|
does not replace the image in the root disk so the API behavior was always
|
|
wrong and is now explicit about the failure.
|
|
|
|
.. _bug 1482040: https://bugs.launchpad.net/nova/+bug/1482040
|