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.
Description of problem:
Running a sosreport in RHEL 7 against an openshift node takes forever or does not complete.
The jars plugin scans a wide variety of paths looking for JAR files:
/usr/lib/python2.7/site-packages/sos/plugins/jars.py lists these default paths
# There is no standard location for JAR files and scanning
# the whole filesystem could be very slow. Therefore we only
# scan directories in which JARs can be typically found.
jar_locations = (
"/usr/share/java", # common location for JARs
"/usr/lib/java", # common location for JARs containing native code
"/opt", # location for RHSCL and 3rd party software
"/usr/local", # used by sysadmins when installing SW locally
"/var/lib" # Java services commonly explode WARs there
)
OpenShift / Docker mounts docker volumes to /var/lib/origin/openshift.local.volumes/, so a large environment leads to significant delays or failure to ever complete due to the JARs plugin.
Version-Release number of selected component (if applicable):
RHEL 7.4
How reproducible:
100%
Steps to Reproduce:
1. try collect sosreport from an OCP environment with a lot of mounts and containers.
Actual results:
Runs for a LONG time.
Expected results:
Completed quickly.
Additional info:
Description of problem: Running a sosreport in RHEL 7 against an openshift node takes forever or does not complete. The jars plugin scans a wide variety of paths looking for JAR files: /usr/lib/python2.7/site-packages/sos/plugins/jars.py lists these default paths # There is no standard location for JAR files and scanning # the whole filesystem could be very slow. Therefore we only # scan directories in which JARs can be typically found. jar_locations = ( "/usr/share/java", # common location for JARs "/usr/lib/java", # common location for JARs containing native code "/opt", # location for RHSCL and 3rd party software "/usr/local", # used by sysadmins when installing SW locally "/var/lib" # Java services commonly explode WARs there ) OpenShift / Docker mounts docker volumes to /var/lib/origin/openshift.local.volumes/, so a large environment leads to significant delays or failure to ever complete due to the JARs plugin. Version-Release number of selected component (if applicable): RHEL 7.4 How reproducible: 100% Steps to Reproduce: 1. try collect sosreport from an OCP environment with a lot of mounts and containers. Actual results: Runs for a LONG time. Expected results: Completed quickly. Additional info: