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.

The 'crio config' command dumps the merged runtime config for the cri-o daemon/service.  This is a merged version of /etc/crio/crio.conf and any overrides/modifications in /etc/crio/crio.d/.  Please collect the output of 'crio config' when running sosreport on RHEL CoreOS.

If sos report will already collect /etc/crio/crio.conf and /etc/crio/crio.d/ (see bz1881118), do we need to collect also their merged version?

It isnt a problem to add the command collection per se, just checking if sosreport wont collect some duplicated information.

(In reply to Pavel Moravec from comment #2)
> If sos report will already collect /etc/crio/crio.conf and /etc/crio/crio.d/
> (see bz1881118), do we need to collect also their merged version?
> 
> It isnt a problem to add the command collection per se, just checking if
> sosreport wont collect some duplicated information.

Hello,
could you please answer this question? Isn't the requested data a duplicate of what is being asked in bz1881118 ?

I believe it would be helpful to see the full, merged config so that we don't have to guess/manually determine the inheritance/overrides based solely on what's in /etc/crio/crio.conf.d/

Thanks, upstream PR raised, added to scope 8.5.

This should have been fixed in RHEL8.5, so closing it. If there is an issue with the fix, please reopen the BZ.