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:
Currently, broken symlinks are not collected as stat-ing the file fails. Anyway if a plugin requests to collect some path that is a broken symlink, having the information about the destination and also the fact the symlink is broken, both the pieces of information are valuable to collect.

Simply saying, sos report should collect files that are broken symlinks (if a plugin requests that).


Version-Release number of selected component (if applicable):
sos-4.0-2


How reproducible:
100%


Steps to Reproduce:
1. let sos to attempt to collect a broken symlink:
mkdir -p /etc/qpid
rm -rf /etc/qpid/qpidd.conf
ln -s /etc/qpid/qpidd.conf-broken /etc/qpid/qpidd.conf
sos report -o qpid --batch --build -vvv

2. check if the generated directory does contain etc/qpid/qpidd.conf .


Actual results:
2. does not contain it, due to logging "failed to stat '/etc/qpid/qpidd.conf'"


Expected results:
2. to contain it, despite logging that info.


Additional info:

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:1604