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.

There are no longer package names shipped as part of Red Hat Discovery. Previously we looked for;
~~~
    packages = ('discovery', 'discovery-tools',)
~~~

But these no longer exist. Only container deployment on base rhel is the delivery method now. The container names remain the same and 'discovery' and 'dsc-db' logs are still the most important. Without RPMs though I'm unsure how sos would determine how to enable the plugin.

New log locations are;
~~~
/var/lib/containers/storage/volumes/dsc-data/_data/userdata/log/ (psql logs)
/var/discovery/server/volumes/log/ (app and quipucords log)
~~~

Thank you for the bug report Paul. We can check if a container with a certain name is running, and if so, capture the data. Just to verify, the container names will contain 'discovery' and/or 'discovery-tools'?

Excellent, thank you. The container names to grab data from are 'dsc-db' and 'discovery'.

I raised https://github.com/sosreport/sos/pull/3324 . I left the current plugin triggers (packages) there for legacy reasons.

Let me know if whole directories are required to be collected, or (e.g. due to log size limit imposed by default) just some specific log files should be grabbed.

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-2023:5354