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:
crio parsing output got broken for sos.
That leads to OCP-specific features of sos not being enabled.
We are planning to release it with Openshift 4.11, code freeze is on June 24th, therefore the urgency is high.

Version-Release number of selected component (if applicable):
rpm version is sos-4.2-19

How reproducible:
Always

Steps to Reproduce:
1. Run sos collect for OCP nodes
2. check openshift-ovn plugin wasn't enabled

Expected results:
openshift-ovn should be enabled and collected

This should be resolved by upstream PR https://github.com/sosreport/sos/pull/2949

Mirek,
please assess the possibility of releasing the bugfix in an 8.6.z batch from QE perspective.

Hi Nadia,
just to confirm: any backport that will happen (no promise/commitment from our side, yet), you will be able to verify the fix, right?

Thanks for acknowledging and expected commitment.

Hey Pavel, sure I will, I really need this fix to get to 4.11 :)

Hi Nadia,
could you please elaborate on severity of the bug? I.e. how much would be support engineers affected by missing data from the plugin?

That would help us prioritize BZs / decide about z-stream.

Thanks in advance.

This BZ will be fixed in 8.7 and cloned to 8.6.z. Work in progress on that..

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 (sos bug fix and enhancement update), 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-2022:7732