Bug 1976300 - OSP16.2 No Validations Execute
Summary: OSP16.2 No Validations Execute
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: validations-common
Version: 16.2 (Train)
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: beta
: 16.2 (Train on RHEL 8.4)
Assignee: mathieu bultel
QA Contact: nlevinki
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-06-25 17:43 UTC by David Rosenfeld
Modified: 2022-01-20 11:00 UTC (History)
7 users (show)

Fixed In Version: validations-common-1.1.2-2.20210611010116.el8ost.2
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-09-15 07:16:23 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1933515 0 None None None 2021-06-28 12:25:27 UTC
OpenStack gerrit 798144 0 None NEW Release validations-common 1.1.2 for stable/train backward compatibility 2021-08-11 09:28:15 UTC
RDO 34298 0 None None None 2021-06-25 19:06:37 UTC
RDO 34307 0 None None None 2021-06-28 07:09:14 UTC
Red Hat Issue Tracker OSP-5476 0 None None None 2022-01-20 11:00:55 UTC
Red Hat Issue Tracker VALFRWK-575 0 None None None 2021-08-13 05:46:39 UTC
Red Hat Product Errata RHEA-2021:3483 0 None None None 2021-09-15 07:17:00 UTC

Description David Rosenfeld 2021-06-25 17:43:36 UTC
Description of problem: In latest OSP 16.2 build no validations return anything. Example:

openstack tripleo validator run --validation no-op
Running Validations without Overcloud settings.


Version-Release number of selected component (if applicable): RHOS-16.2-RHEL-8-20210623.n.1


How reproducible: Every time 


Steps to Reproduce:
1. Execute a validator like the no-op validator shown above.
2.
3.

Actual results: Validator does not execute.


Expected results: Validator executes and prints pass/fail status


Additional info:

Comment 1 mathieu bultel 2021-06-25 17:49:47 UTC
We need to tag and pin validations-common for stable/train to avoid backward compat.

Comment 3 Gaël Chamoulaud 2021-06-28 08:49:58 UTC
When running validations, the validation_json.py Ansible Callback is logging
in ~/home/stack instead of the /var/log/validations directory. Although the
title of this BZ says they are not, the validations are really executed but
the log interpretation is unfortunately not done because the logs are not
where they should be.

Commit introducing the regression is https://opendev.org/openstack/validations-common/commit/f07c8e73bbed4411830aedeadca36b0f0f270274

Comment 6 Jad Haj Yahya 2021-07-08 07:56:21 UTC
Automated job passed

Comment 9 errata-xmlrpc 2021-09-15 07:16:23 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 (RHOSP) 16.2 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/RHEA-2021:3483


Note You need to log in before you can comment on or make changes to this bug.