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

Bug 2056602

Summary: Running "openstack overcloud deploy" with "--run-validations" and no overcloud leads to an inventory error and crash
Product: Red Hat OpenStack Reporter: Jiri Podivin <jpodivin>
Component: openstack-tripleo-validationsAssignee: mathieu bultel <mbultel>
Status: CLOSED EOL QA Contact: Nobody <nobody>
Severity: high Docs Contact:
Priority: high    
Version: 16.1 (Train)CC: jjoyce, jschluet, slinaber, tvignaud
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-09-18 19:22:54 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: 1974353    

Description Jiri Podivin 2022-02-21 15:02:40 UTC
Description of problem:

During the testing of BZ#1974353 a new error was encountered caused by erroneous inventory generation by the tripleo-ansible-inventory script.

The resulting inventory contains circular reference to a group, making it invalid. This forces mistral to fallback on YAML/JSON parsing, which leads to exceptions as a python script is not a YAML nor JSON.

This is possibly another manifestation of the BZ#1887444 .

Trace:
------
 Failed to parse /usr/bin/tripleo-ansible-inventory with script\nplugin: can't add group to itself\n[WARNING]:  * Failed to parse /usr/bin/tripleo-ansible-inventory with yaml\nplugin: We were unable to read either as JSON nor YAML, these are the errors we\ngot from each: JSON: Expecting value: line 1 column 

Version-Release number of selected component (if applicable):
openstack-tripleo-validations-11.3.2-1.20210913123540.4db92ba.el8ost.noarch

How reproducible:
Always


Steps to Reproduce:
1.Execute overcloud deployment on stack with no undercloud.
2.
3.

Actual results:
Exception

Expected results:

Oercloud deployment.

Additional info: