Bug 1572379
Summary: | nodes in ironic still point to older ram and kernel after images update in glance. | |||
---|---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Alexander Chuzhoy <sasha> | |
Component: | python-tripleoclient | Assignee: | RHOS Maint <rhos-maint> | |
Status: | CLOSED ERRATA | QA Contact: | Alexander Chuzhoy <sasha> | |
Severity: | medium | Docs Contact: | ||
Priority: | medium | |||
Version: | 13.0 (Queens) | CC: | bfournie, hbrock, jslagle, lmarsh, mburns, rhos-maint, srevivo | |
Target Milestone: | z3 | Keywords: | Triaged, ZStream | |
Target Release: | 13.0 (Queens) | Flags: | lmarsh:
needinfo-
lmarsh: needinfo- |
|
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | python-tripleoclient-9.2.6-2.el7ost | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 1699832 (view as bug list) | Environment: | ||
Last Closed: | 2018-11-13 22:26:39 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: | ||||
Bug Blocks: | 1699832 |
Description
Alexander Chuzhoy
2018-04-26 21:43:53 UTC
Isn't this by design as we don't want to affect nodes when we make changes to glance? Bob is right, this is by design. However, I also agree that it is extremely confusing. Maybe we should make the images upload command update nodes as well? Or maybe we should at least make it print "Deploy images updated, run `openstack overcloud node configure` for affected nodes"? Ideas are welcome. I like the message to update the nodes. Verified: Environment: python-tripleoclient-9.2.6-2.el7ost.noarch So this is resolved with a message being prompted to the user/admin upon uploading new images: openstack overcloud image upload --update-existing Image "overcloud-full-vmlinuz" is up-to-date, skipping. Image "overcloud-full-initrd" is up-to-date, skipping. Image "overcloud-full" was uploaded. +--------------------------------------+----------------+-------------+------------+--------+ | ID | Name | Disk Format | Size | Status | +--------------------------------------+----------------+-------------+------------+--------+ | 70731c18-f118-41e6-8643-a2510d5cf9f1 | overcloud-full | qcow2 | 1215299584 | active | +--------------------------------------+----------------+-------------+------------+--------+ Image "bm-deploy-kernel" is up-to-date, skipping. Image "bm-deploy-ramdisk" is up-to-date, skipping. Image file "/httpboot/agent.kernel" is up-to-date, skipping. Image file "/httpboot/agent.ramdisk" is up-to-date, skipping. Some images have been updated in Glance, make sure to rerun openstack overcloud node configure to reflect the changes on the nodes 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:3587 |