Description of problem: The Custom callback feature is not working anymore since the introduction of the configuration file [1] for the VF. Passing --extra-env-vars ANSIBLE_STDOUT_CALLBACK through the openstack tripleo validator run sub command is not effective anymore. How reproducible: Steps to Reproduce: $ openstack tripleo validator run --validation check-cpu --extra-env-vars ANSIBLE_STDOUT_CALLBACK=default Actual results: (undercloud) [stack@undercloud ~]$ openstack tripleo validator run --validation check-cpu --inventory ~/overcloud-deploy/overcloud/tripleo-ansible-inventory.yml --extra-env-vars ANSIBLE_STDOUT_CALLBACK=default +--------------------------------------+-------------+--------+------------+----------------+-------------------+-------------+ | UUID | Validations | Status | Host_Group | Status_by_Host | Unreachable_Hosts | Duration | +--------------------------------------+-------------+--------+------------+----------------+-------------------+-------------+ | 89fe85a1-aa1a-4e94-9e24-b7e608c21457 | check-cpu | FAILED | localhost | localhost | | 0:00:00.677 | +--------------------------------------+-------------+--------+------------+----------------+-------------------+-------------+ One or more validations have failed. Expected results: (undercloud) [stack@undercloud-0 ~]$ openstack tripleo validator run --validation check-cpu --inventory ~/overcloud-deploy/overcloud/tripleo-ansible-inventory.yml --extra-env-vars ANSIBLE_STDOUT_CALLBACK=default Running Validations without Overcloud settings. PLAY [localhost] *************************************************************** TASK [check_cpu : Gather facts] ************************************************ Wednesday 13 October 2021 08:01:37 -0400 (0:00:00.037) 0:00:00.037 ***** ok: [localhost] TASK [check_cpu : Verify the number of CPU cores] ****************************** Wednesday 13 October 2021 08:01:38 -0400 (0:00:00.825) 0:00:00.863 ***** fatal: [localhost]: FAILED! => {"changed": false, "failed_when_result": true, "msg": "There are 4 cores in the system, but there should be at least 8"} PLAY RECAP ********************************************************************* localhost : ok=1 changed=0 unreachable=0 failed=1 skipped=0 rescued=0 ignored=0 Wednesday 13 October 2021 08:01:38 -0400 (0:00:00.113) 0:00:00.977 ***** =============================================================================== check_cpu : Gather facts ------------------------------------------------ 0.83s check_cpu : Verify the number of CPU cores ------------------------------ 0.11s +--------------------------------------+-------------+--------+------------+----------------+-------------------+-------------+ | UUID | Validations | Status | Host_Group | Status_by_Host | Unreachable_Hosts | Duration | +--------------------------------------+-------------+--------+------------+----------------+-------------------+-------------+ | 5a0e43b3-eb33-48ab-b2f3-c36c0dbb2674 | check-cpu | FAILED | localhost | localhost | | 0:00:00.953 | +--------------------------------------+-------------+--------+------------+----------------+-------------------+-------------+ One or more validations have failed. Additional info: [1] https://opendev.org/openstack/validations-libs/commit/11488cd88d6caca0e9e41d589936ec525d62eea4
Manually tested and verified on RHOS-17.0-RHEL-9-20220816.
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