Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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.

If the rpm command times out during initial policy setup we will fail to start sosreport if the list of packages read before the timeout does not include the 'filesystem' package. This is because the version of this package is checked to determine the correct PATH setting (taking account of UsrMove).

This was addressed upstream via PR 942:

  https://github.com/sosreport/sos/pull/942

Following this change the initial read of the RPMDB is carried out with no timeout. Users with very large databases or very busy systems may see a pause while sos starts up but policy will be correctly set and the run will complete as normal.

Is there any way to workaround it and still gather the sosreports?

(In reply to Marina from comment #2)
> Is there any way to workaround it and still gather the sosreports?

Two independent options/workarounds are there:

- ensure by either way that "rpm -qa" like command finishes within 30 seconds

- or apply the patch from [1] to /usr/lib/python2.6/site-packages/sos/policies/__init__.py (officially not supported as not shipped, but shall work well)


[1] https://github.com/sosreport/sos/pull/942/files

*** This bug has been marked as a duplicate of bug 1506596 ***