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.
Bug 1930181 - collect --clean does not work reliably
Summary: collect --clean does not work reliably
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: sos
Version: 8.4
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Pavel Moravec
QA Contact: Miroslav Hradílek
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-02-18 13:34 UTC by Miroslav Hradílek
Modified: 2021-11-10 07:38 UTC (History)
6 users (show)

Fixed In Version: sos-4.1-2.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-11-09 19:36:07 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github sosreport sos pull 2492 0 None open [clean] Improve collect cleaning consistency 2021-04-14 18:14:05 UTC
Red Hat Product Errata RHEA-2021:4388 0 None None None 2021-11-09 19:36:18 UTC

Description Miroslav Hradílek 2021-02-18 13:34:08 UTC
Description of problem:
When using cleaner as part of "sos collect" command the archives on nodes are not reliably obfuscated.

Version-Release number of selected component (if applicable):
sos-4.0-8.el8.noarch

How reproducible:
50%

Steps to Reproduce:
1. ssh-keygen -t rsa -f $HOME/.ssh/id_rsa -N ''
2. ssh-copy-id root.com
3. sos collect --cluster-type jbon --node node.hostname.com -o host -o networking -o logs --batch --clean

Actual results:
Inside the collector created archive, the sosreport archives are not obfuscated properly. This depends on versions of "sos" on master and '--node' specified node and also somehow on chance. Sometimes not even hostname is removed from the archive name (collected from '--node' specified given node). Sometimes hostname is only removed from some files containing it both on master node and a given node.

Expected results:
Everything is removed just like if "sos clean" was called on each sosreport archive individually.

Comment 2 Jake Hunsaker 2021-04-14 18:14:09 UTC
I believe this will be addressed via upstream PR https://github.com/sosreport/sos/pull/2492

Comment 7 errata-xmlrpc 2021-11-09 19:36:07 UTC
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/RHEA-2021:4388


Note You need to log in before you can comment on or make changes to this bug.