yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #65078
[Bug 1497484] Re: image-create does not respect the force_raw_images setting
** Changed in: nova/mitaka
Status: Fix Committed => Fix Released
--
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/1497484
Title:
image-create does not respect the force_raw_images setting
Status in OpenStack Compute (nova):
Fix Released
Status in OpenStack Compute (nova) mitaka series:
Fix Released
Bug description:
Instance snapshots of instances sourced from, e.g., QCOW2 images will
be created in the image service as "qcow2" and then switched to "raw"
in an update step.
Use case:
We decided to drop QCOW2 support from certain product configurations,
as force_raw_images is enabled by default, and the conversion overhead
made for a sub-wonderful customer experience.
After dropping QCOW2 from the acceptable list of image formats from
Glance, clients could no longer make instance snapshots from instances
that were spawned from QCOW2 images, despite the fact that the backing
store was not QCOW2.
Steps to Reproduce:
1. Upload a QCOW2 image into Glance
2. Update Nova/Glance configs to disable QCOW2 images and enable force_raw_images
3. Boot an instance against the QCOW2 image
4. Create a snapshot of the instance
Expected behavior:
A snapshot of the instance
Actual results:
ERROR (BadRequest): <html>
<head>
<title>400 Bad Request</title>
</head>
<body>
<h1>400 Bad Request</h1>
Invalid disk format 'qcow2' for image.<br /><br />
</body>
</html> (HTTP 400) (HTTP 400) (Request-ID: req-8e8d8d51-8e0c-4033-bb84-774d2ed1f90a)
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1497484/+subscriptions
References
