So this behavior happens when glanceclient already received image information. You can at least get an info trhough API as workaround. The root cause is in schema validation after receiving this info. Need to think more about this case.
** Project changed: glance => python-glanceclient -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1501046 Title: v2 API: Not possible to "retire" disk formats Status in python-glanceclient: New Bug description: Use case: We tried to remove QCOW2 from the list of supported disk_formats in some of our deployments, because the conversion overhead of using them was making for a sub-wonderful user experience. After removing "qcow2" from the disk_formats parameter, the Glance v2 API started returning 404 errors on extant QCOW2 images. This means that we effectively cannot "retire" this disk format and block new image uploads, since Glance will immediately disavow all knowledge of any QCOW2 images in its purview. Steps to Reproduce: 1. Stand up a devstack 2. Upload a QCOW2 image 3. glance --os-image-api-version 2 image-show IMAGE_ID 4. Reconfigure glance-api to only allow e.g., "raw" disk_formats: [image_format] disk_formats = raw,ami,ari,aki,iso 5. Restart glance-api 6. glance --os-image-api-version 2 image-show IMAGE_ID Expected results: The "glance image-show" command works both times Actual results: The second "glance image-show" command fails. Errata: The "glance image-show" using the v1 API does work as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/python-glanceclient/+bug/1501046/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
