Bug 2122932

Summary: VF runtime doesn't respect inventory path specified in the validation.cfg
Product: Red Hat OpenStack Reporter: Jiri Podivin <jpodivin>
Component: python-validations-libsAssignee: mathieu bultel <mbultel>
Status: CLOSED ERRATA QA Contact: nlevinki <nlevinki>
Severity: high Docs Contact:
Priority: high    
Version: 17.0 (Wallaby)CC: jschluet, mbultel
Target Milestone: z1Keywords: Bugfix, Triaged
Target Release: 17.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python-validations-libs-1.7.2-0.20221208090406.b27ad5a.el9ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-01-25 12:28:51 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 Jiri Podivin 2022-08-31 10:20:21 UTC 
Description of problem:

Inventory key in the validation.cfg file is meant to supply default path to ansible inventory. However, CLI ignores contents of the field 

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


How reproducible:
Always.

Steps to Reproduce:
1. Set inventory key in the validation.cfg file
2. Execute VF run

Actual results:
Inventory isn't used

Expected results:
Inventory should be used in preference to the default 'localhost'.

Additional info:
Issue appears to be caused by inconsistent handling of the data obtained from parsed cfg file. The `self.base.config` attribute contains empty dictionary, due to the 'base' object being reinitialized in the meantime. 

Furthermore, as the inventory key exists in the 'ansible-runner' section, it won't be read by the runtime before execution of the valdiation, as the run command only requests content of the default section.
Comment 12 errata-xmlrpc 2023-01-25 12:28:51 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 (Red Hat OpenStack Platform 17.0.1 bug fix and enhancement 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-2023:0271
Comment 13 Red Hat Bugzilla 2023-09-19 04:25:24 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days