Bug 1779356 - update prepare/run commands always saving config to overcloud-config container regardless of stack name
Summary: update prepare/run commands always saving config to overcloud-config containe...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-common
Version: 16.0 (Train)
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ga
: 16.0 (Train on RHEL 8.1)
Assignee: James Slagle
QA Contact: Yuri Obshansky
URL:
Whiteboard:
Depends On:
Blocks: 1710461
TreeView+ depends on / blocked
 
Reported: 2019-12-03 19:54 UTC by James Slagle
Modified: 2020-02-06 14:43 UTC (History)
5 users (show)

Fixed In Version: openstack-tripleo-common-11.3.1-1 python-tripleoclient-12.3.0-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-02-06 14:43:39 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1854991 0 None None None 2019-12-03 19:57:51 UTC
OpenStack gerrit 700050 0 None MERGED Pass container_config to config actions 2021-01-22 21:42:01 UTC
OpenStack gerrit 700051 0 None MERGED Pass container name to update_nodes workflow 2021-01-22 21:42:01 UTC
Red Hat Product Errata RHEA-2020:0283 0 None None None 2020-02-06 14:43:56 UTC

Description James Slagle 2019-12-03 19:54:43 UTC
The update prepare command calls the get_config workflow from workbooks/package_update.py. This workflow calls the tripleo.config.get_overcloud_config action, but it only passes in the container name, not the container_config name.

This means the action ends using overcloud-config, even if the stack name is called something not overcloud. This can cause issues with multi-stack and the multiple overcloud features, or just using a non default overcloud name.

Comment 5 errata-xmlrpc 2020-02-06 14:43:39 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/RHEA-2020:0283


Note You need to log in before you can comment on or make changes to this bug.