Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1829322

Summary:	[OSP16.1] Custom stack name not working during deployment/upgrade.
Product:	Red Hat OpenStack	Reporter:	Jose Luis Franco <jfrancoa>
Component:	openstack-tripleo-common	Assignee:	Ollie Walsh <owalsh>
Status:	CLOSED ERRATA	QA Contact:	David Rosenfeld <drosenfe>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	16.1 (Train)	CC:	jpretori, mburns, owalsh, slinaber
Target Milestone:	beta	Keywords:	Triaged
Target Release:	16.1 (Train on RHEL 8.2)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-tripleo-common-11.3.3-0.20200430033430.e1c4f45.el8ost	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-07-29 07:52:15 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 Jose Luis Franco 2020-04-29 11:42:47 UTC

Description of problem:

deploy-steps.j2 currently defaults to 'overcloud' for the deployment_target_hosts param.

Before [0] merged, the "overcloud" group always existed in the tripleo ansible inventory. Now this is only true when there is an "overcloud" heat stack. The "allovercloud" group is now used to refer to all overcloud hosts.

While the param could switch to allovercloud, it would fail in future if we ever ran it with a multi-stack inventory, so it would be more correct to use the <stack_name> inventory group as the default.

[0] - https://review.opendev.org/#/c/718557/

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.Deploy OSP with custom stack name qe-Cloud-0
2.
3.

Actual results:

Deployment/upgrade fails because the 'overcloud' Ansible group can't be found.

Expected results:

Deployment/upgrade succeeds.

Additional info:

Comment 7 David Rosenfeld 2020-05-12 13:25:05 UTC

Specified a non default stack name(qe-Cloud-0) in infrared and did a deployment. Deployment was successful. Checked stack name:

(undercloud) [stack@undercloud-0 ~]$ openstack stack list
+--------------------------------------+------------+----------------------------------+-----------------+----------------------+--------------+
| ID                                   | Stack Name | Project                          | Stack Status    | Creation Time        | Updated Time |
+--------------------------------------+------------+----------------------------------+-----------------+----------------------+--------------+
| b9422f34-a8fb-4a1d-97d1-6502e4e03a64 | qe-Cloud-0 | 1e653f2596494902b3912555635ac849 | CREATE_COMPLETE | 2020-05-12T01:26:56Z | None         |
+--------------------------------------+------------+----------------------------------+-----------------+----------------------+--------------+

Comment 8 Alex McLeod 2020-06-16 12:29:55 UTC

If this bug requires doc text for errata release, please set the 'Doc Type' and provide draft text according to the template in the 'Doc Text' field. The documentation team will review, edit, and approve the text.

If this bug does not require doc text, please set the 'requires_doc_text' flag to '-'.

Comment 10 errata-xmlrpc 2020-07-29 07:52:15 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-2020:3148