Bug 1244139
| Summary: | Updating overcloud-full image breaks deployments | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Steven Hardy <shardy> |
| Component: | rhosp-director | Assignee: | Marek Aufart <maufart> |
| Status: | CLOSED DUPLICATE | QA Contact: | yeylon <yeylon> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | high | ||
| Version: | unspecified | CC: | calfonso, jslagle, maufart, mburns, rhel-osp-director-maint, srevivo |
| Target Milestone: | z1 | Keywords: | Triaged |
| Target Release: | Director | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-07-24 16:29:53 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
Steven Hardy
2015-07-17 09:46:22 UTC
the overcloud-full kernel and ramdisk id's are saved as glance properties on the qcow2 image: [stack@instack ~]$ glance image-show 6e5c161b-d31e-47e2-82c9-8cb80ae8ce04 +-----------------------+--------------------------------------+ | Property | Value | +-----------------------+--------------------------------------+ | Property 'kernel_id' | 00d1c4ab-137a-4135-8095-c78a4af3dcc3 | | Property 'ramdisk_id' | a5bd6e54-0274-45f8-af87-0d8c42364b5f | | checksum | fae896e079de34860c78d39baca3301a | | container_format | bare | | created_at | 2015-07-14T21:39:25.000000 | | deleted | False | | disk_format | qcow2 | | id | 6e5c161b-d31e-47e2-82c9-8cb80ae8ce04 | | is_public | True | | min_disk | 0 | | min_ram | 0 | | name | overcloud-full | | owner | 8027be3dc82b4bf7a91c3e25c2622aad | | protected | False | | size | 914223616 | | status | active | | updated_at | 2015-07-14T21:39:31.000000 | +-----------------------+--------------------------------------+ I think this is probably your issue since you're trying to reuse the old vmlinuz/initrd with the new image. Totally agree this needs documentation. @James: Aha!! Thanks, I totally missed that. I guess this could be considered a dupe of bz#1243829 then, as if we correctly handle reloading the image without creating the dupes, I probably wouldn't have got into this state. Docs patch also sounds like a good plan tho. This has impact on partners and needs to be resolved for any updates in an A1 timeframe Marek, what are you doing with this bug given comment 4 notes a potential dupe. (In reply to chris alfonso from comment #6) > Marek, what are you doing with this bug given comment 4 notes a potential > dupe. I am working on bz#1243829. It is duplicate from functional point of view. I considered if this bug would result to docs update, but propably no (it should not happend when duplicate one is fixed). Going to close this one as duplicate of bz#1243829 and mark the duplicate one as blocker since this one has blocker ?. *** This bug has been marked as a duplicate of bug 1243829 *** |