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

Bug 2050765

Summary: tripleo validator run doesn't generate the inventory on-the-fly anymore
Product: Red Hat OpenStack Reporter: David Vallee Delisle <dvd>
Component: openstack-tripleo-validationsAssignee: mathieu bultel <mbultel>
Status: CLOSED WONTFIX QA Contact: nlevinki <nlevinki>
Severity: medium Docs Contact:
Priority: medium    
Version: 16.2 (Train)CC: astillma, cjeanner, dhill, drosenfe, gregraka, jjoyce, jparker, jpodivin, jpretori, jschluet, mbultel, ravsingh, rhayakaw, slinaber, tvignaud
Target Milestone: z3Keywords: Triaged
Target Release: 16.2 (Train on RHEL 8.4)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Known Issue
Doc Text:
There is currently a known issue in which the OpenStack `tripleo validator run` command produces errors. In the command output the Status_by_Host column contains the value, 'No host matched'. This error occurs with all `openstack validator run` calls because no ansible inventory was available for the undercloud and is not limited to a single validator group. This error also impacts overcloud validations. The root cause of this is a regression in the tripleo client code where tripleo-ansible-inventory is no longer called in real time. + As a result, in updates to Red Hat OpenStack Platform (RHOSP) 16.2, the `tripleo validator run --group pre-introspection` command fails on all tests. + Workaround: create a file called inventory.yaml by manually running `tripleo-ansible-inventory --static-yaml-inventory inventory.yaml`. Then, run the validation using the `-i inventory.yaml` argument: + ---- # tripleo-ansible-inventory --static-yaml-inventory inventory.yaml # openstack tripleo validator run --group pre-introspection -i inventory.yaml ---- + For more information, see the Red Hat Knowledgebase solution https://access.redhat.com/solutions/6895151[openstack tripleo validator run command produces error].
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-10-06 09:24:46 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: 2072787    

Description David Vallee Delisle 2022-02-04 15:33:17 UTC
Description of problem:
Since 16.2.2, it looks like tripleo validator run doesn't generate the inventory on the fly anymore when the default inventory isn't found

Version-Release number of selected component (if applicable):
python3-tripleo-common-11.7.1-2.20211218004850.173edba.el8ost.noarch           
python3-validations-libs-1.5.0-2.20220115004852.17e6895.el8ost.noarch          
validations-common-1.5.0-2.20220112153836.cf7ebdd.el8ost.noarch                
openstack-tripleo-common-11.7.1-2.20211218004850.173edba.el8ost.noarch         
python3-tripleoclient-heat-installer-12.6.1-2.20220114104840.db6a328.el8ost.noarch
python3-tripleoclient-12.6.1-2.20220114104840.db6a328.el8ost.noarch            
openstack-tripleo-validations-11.6.1-2.20220115004852.c6d8b57.el8ost.noarch    
openstack-tripleo-common-containers-11.7.1-2.20211218004850.173edba.el8ost.noarch

Comment 1 Cédric Jeanneret 2022-02-16 08:33:49 UTC
Hello there,

IMHO best way to correct this issue:

- in tripleoclient, add a new parameter, like "--inventory-file", defaulting to something sensible, such as "~/tripleo-deploy/STACK_NAME/tripleo-ansible-inventory.yaml" - STACK_NAME may default to "overcloud", or "undercloud"
- in VF itself, check for the availability of the inventory_file, and crash if it's absent

Note:
the path is for osp-17, maybe another value would be needed for 16.2? In any cases, 16.2 may require a doc update in order to instruct Operator to generate the inventory before running validations - this is already a known step for FFU (I don't remember which one, probably 13->16, but you'd need someone from Upgrades to get that precision).

I'll let the VF folks decide if this is good for them, and implement the proper solution.

Cheers,

C.

Comment 4 Jiri Podivin 2022-04-08 12:31:10 UTC
*** Bug 2072787 has been marked as a duplicate of this bug. ***

Comment 5 Jiri Podivin 2022-04-13 09:34:03 UTC
*** Bug 2074769 has been marked as a duplicate of this bug. ***

Comment 11 mathieu bultel 2022-10-06 09:24:46 UTC
I'm closing this bug since it has been addressed via the Documentation.