Bug 1623968
| Summary: | [BACKPORT] openstack-nova: check that the image data is not None | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Stephen Finucane <stephenfin> |
| Component: | openstack-nova | Assignee: | Stephen Finucane <stephenfin> |
| Status: | CLOSED ERRATA | QA Contact: | OSP DFG:Compute <osp-dfg-compute> |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | 12.0 (Pike) | CC: | berrange, dasmith, dcadzow, eglynn, fpercoco, jhakimra, kchamart, lyarwood, mbooth, owalsh, sasha, sbauza, sclewis, sgordon, srevivo, stephenfin, vromanso |
| Target Milestone: | z4 | Keywords: | FeatureBackport, TestOnly, Triaged, ZStream |
| Target Release: | 12.0 (Pike) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | openstack-nova-16.0.4-5.el7ost | Doc Type: | Bug Fix |
| Doc Text: |
Cause:
glanceclient can return 'None' from 'glanceclient.v2.images.Controller.data'. This is a valid value but nova was not handling it.
Consequence:
An unhandled error would be raised when booting an instance, resulting in a HTTP 500 error from nova-api.
Fix:
nova will now handle these values and raise an exception that can be handled by nova-api.
Result:
Users will now see a meaningful error message highlighting issues with the images returned by glance.
|
Story Points: | --- |
| Clone Of: | 1481787 | Environment: | |
| Last Closed: | 2018-12-05 18:50:50 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1476448, 1481787, 1486995 | ||
| Bug Blocks: | 1481838 | ||
|
Comment 2
Lon Hohberger
2018-08-31 12:17:36 UTC
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:3791 |