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.
DescriptionJuan Orti Alcaine
2019-08-30 07:38:59 UTC
Description of problem:
Sometimes I get the error "Fatal error: nothing to repeat" when running sos-collector on multiple servers and with a --tmp-dir
# sos-collector --tmp-dir /var/tmp/sos --nodes rhvh1,rhvh2,rhvm --master rhvm
[...]
The following is a list of nodes to collect from:
rhvm
rhvh1
rhvh2
Please enter the case id you are collecting reports for:
Connecting to nodes...
Beginning collection of sosreports from 3 nodes, collecting a maximum of 4 concurrently
rhvm : Generating sosreport...
rhvh1 : Generating sosreport...
rhvh2 : Generating sosreport...
rhvh1 : Retrieving sosreport...
rhvh1 : Successfully collected sosreport
rhvh2 : Retrieving sosreport...
rhvh2 : Successfully collected sosreport
rhvm : Retrieving sosreport...
rhvm : Successfully collected sosreport
Collecting additional data from master node...
Successfully captured 3 of 3 sosreports
Creating archive of sosreports...
Fatal error: nothing to repeat
Version-Release number of selected component (if applicable):
sos-collector-1.7-5.el7.noarch
How reproducible:
Sometimes
Steps to Reproduce:
1. Run sos-collector on multiple systems with --tmp-dir
Actual results:
Fatal error: nothing to repeat
Expected results:
No error
Additional info:
The generated sosreport tarball looks good.
The customer thinks this may be the problem:
If the thread count is lower than the number of nodes (Hosts+RHV-M) in the cluster, then at the end of the run we see this error even though the run seems to have been ok.
After discussing this with QA, we will be addressing this in 7.8.z with an update to sos-collector-1.8.
In the meantime, for anyone hitting this bug, note that the sosreports _are_ still collected and exist on the system where sos-collector was run. If you look in the temp directory provided, you'll see the collected sosreports and their md5 sums - thus as a workaround, please manually create a tar archive of the sosreports to provide to your support engineer via your support case.
I am unsure how or why this bug was not attached to an erratum, but this issue has been resolved for some time via sos-collector-1.8 in both 7.8.Z and 7.9.