Bug 2096427

Summary:	OSP17 dry run fails due to missing overcloud.json file
Product:	Red Hat OpenStack	Reporter:	David Rosenfeld <drosenfe>
Component:	openstack-tripleo-heat-templates	Assignee:	Rabi Mishra <ramishra>
Status:	CLOSED ERRATA	QA Contact:	David Rosenfeld <drosenfe>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	17.0 (Wallaby)	CC:	bshephar, cjeanner, hbrock, jschluet, jslagle, mburns, ramishra, slinaber
Target Milestone:	beta	Keywords:	Triaged
Target Release:	17.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-tripleo-heat-templates-14.3.1-0.20220701162329.dd13d73.el9ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-09-21 12:22:30 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 David Rosenfeld 2022-06-13 19:12:17 UTC

Description of problem: A dry run is performed by executing ansible-playbook command with --check option. This fails with following error:

Could not find or access '/home/stack/overcloud-deploy/overcloud/config-download/overcloud/group_vars/overcloud.json



Version-Release number of selected component (if applicable): RHOS-17.0-RHEL-9-20220610.n.0


How reproducible: Every time


Steps to Reproduce: 
1. deploy overcloud with --stack-only and --setup-only options
2. Execute command: ansible-playbook --check --become -i /home/stack/overcloud-deploy/overcloud/config-download/overcloud/tripleo-ansible-inventory.yaml --key-file ~/.ssh/id_rsa_tripleo /home/stack/overcloud-deploy/overcloud/config-download/overcloud/deploy_steps_playbook.yaml

Note: executing the same command without the --check option is successful.
3.

Actual results: dry-run fails with error above.  


Expected results: dry-run is successful.


Additional info:

Comment 2 Brendan Shephard 2022-06-14 05:24:17 UTC

So, we're doing this before the overcloud has even been deployed then? I'm not sure what use that would actually be, since there would be nothing to check?

It looks like we probably don't export that file with stack-only setup-only. But I just wanted to clarify the use case as I can't envision a scenario where we would want to run ansible-playbook --check without a deployed environment to check against?

This should work without any changes after the overcloud has already been deployed though. We can probably add the steps in to create that file if there is a use case that I'm unaware of.

Comment 7 David Rosenfeld 2022-07-12 17:25:53 UTC

During Phase 3 execution of RHOS-17.0-RHEL-9-20220711.n.1 did not get the missing file during the dry run test

Comment 11 errata-xmlrpc 2022-09-21 12:22:30 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 (Release of components for Red Hat OpenStack Platform 17.0 (Wallaby)), 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-2022:6543