Bug 1470409
| Summary: | launching instance with volume created from snapshot doesn't honor original image min_disk | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Siggy Sigwald <ssigwald> |
| Component: | python-django-horizon | Assignee: | Beth White <beth.white> |
| Status: | CLOSED ERRATA | QA Contact: | Radomir Dopieralski <rdopiera> |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | 10.0 (Newton) | CC: | akaris, athomas, beth.white, jschluet, mrunge, pgrist, rdopiera, srevivo, tshefi |
| Target Milestone: | Upstream M3 | Keywords: | Triaged |
| Target Release: | 13.0 (Queens) | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | python-django-horizon-13.0.1-0.20180411230905.c51a46e.el7ost | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-06-27 13:32:14 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: | |||
|
Description
Siggy Sigwald
2017-07-12 23:59:14 UTC
Hello, Just to see if we can get any ETA or at least traction for this. Regards, Andreas To be honest this looks like a Horizon issue of a missing automation/wizard which being missing doesn't automatically suggest volume size when using snapshots as source. CLI boot of an insufficient volume size, returns same error. # nova boot clinst --flavor 1 --block-device source=image,id=9aeb9b3e-6796-48ee-b4df-0c5af94bcc41,dest=volume,size=1,shutdown=preserve,bootindex=0 ERROR (BadRequest): Volume is smaller than the minimum size specified in image metadata. Volume size is 2147483648 bytes, minimum size is 3221225472 bytes. (HTTP 400) (Request-ID: req-786cba69-bca0-4d52-9361-f1302a2962f6) Here is what I did on Horizon: 1. Uploaded Cirros image, set min-disk to 2G. 2. Booted an instance from Cinder volume 3G, created from above image. 3. Snapshoted the new instance, which created a new snapshot(image) with 3G as min-disk set. 4. I did notice both the correct flow, Horizon boot use image auto set vol size, as well as bad flow Horizon use vol snap no flavor selected. 5. on cli I attempted to boot an instance create volume (size 2G) from said snap image, which failed with a descriptive error same as shown on shot3.png. I too would prefer to see size in GB rather than bytes agree. 6. However on Horizon, this explain in my mind why this bug is a Horizon issue , when I clicked under images tab the "launch" button next to snap(image) the new volume size is selected automatically. IMHO this is a half baked Horizon "wizard/automation" that works as expected, only if you initiate instance booting from image tab snapshot lunch. As if you start it from instance tab launch it doesn't kick in. Cinder isn't to blame as it reports and returns data to Horizon. backported to stable/queens 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/RHEA-2018:2086 |