RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
There are some situations where having a config validations based on oslo-config-validator [a] inside a sosreport can help troubleshoot certain issues for GSS.

This can be easily executed with the tripleo-validations called by the same name [b].

This validation is excecuted on all the overcloud nodes, using the operator's environment to have a perfect validation, using containers of the same version.

The goal of this RFE is to integrate the tripleo-validation into a sosreport plugin.

Ideally, we should be able to run any kind of validations, passing any kind of arguments to the validations

[a] https://docs.openstack.org/oslo.config/latest/cli/validator.html
[b] https://docs.openstack.org/tripleo-validations/latest/validations-post-deployment-details.html#oslo-config-validator

I havent received any mail notification about this BZ, hence the BZ is completely new to me :(

No way to get it to 9.0, no guarantee to have it in 9.1 (where granting OtherQE (a will you would self-verify the feature once fixed) increases chances to get the BZ ot the scope). Please clarify if you are willing to test/verify the fix, once available.


The RFE is about calling "just" one command, oslo-config-validator (with some options)? Can you please provide bash pseudocode when and what options to use? Like "if running in container, use --config-file /etc/foo.conf, but --config-file /etc/bar.conf otherwise"?

How long the validator can run? Is default 10 minutes command timeout sufficient? (I would warn if a command takes much time as that prolongs sosreport execution)

I expect the output is always less than 100MB and does not contain any sensitive information like passwords.

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.