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:
sosreport is not capturing /etc/sssd/sssd.conf
Version-Release number of selected component (if applicable):
sos-3.9-5.el7_9.2.noarch
How reproducible:
many customer cases
Example
# rpm -qa | grep sos
sos-3.9-5.el7_9.2.noarch
# sosreport --build --batch -o sssd
sosreport (version 3.9)
This command will collect diagnostic and configuration information from
this Red Hat Enterprise Linux system and installed applications.
An archive containing the collected information will be generated in
/var/tmp/sos.ZZ33Pc and may be provided to a Red Hat support
representative.
Any information provided to Red Hat will be treated in accordance with
the published support policies at:
https://access.redhat.com/support/
The generated archive may contain data considered sensitive and its
content should be reviewed by the originating organization before being
passed to any third party.
No changes will be made to system configuration.
Setting up archive ...
Setting up plugins ...
[plugin:sssd] skipped command 'sssctl config-check': required services missing: sssd.
Running plugins. Please wait ...
Starting 1/1 sssd [Running: sssd]
Finished running plugins
Your sosreport build tree has been generated in:
/var/tmp/sosreport-rhel7-build-2021-04-06-xufvqff
# ls -al /var/tmp/sosreport-rhel7-build-2021-04-06-xufvqff/etc/sssd/sssd.conf
-rw-------. 1 root root 195 6. dub 15.58 /var/tmp/sosreport-rhel7-build-2021-04-06-xufvqff/etc/sssd/sssd.conf
I might know what is going on:
sosreport automatically enables the plugin whenever "sssd" package is installed. If a customer runs "sosreport -[o|e] sssd", it will enable the plugin manually and config file will be collected. Since the config file is present (and sssd functionality available) on the system, sosreport should detect "sssd is present" in more broader way. Since:
# yum provides /usr/sbin/sssd
..
sssd-common-1.16.5-10.el7_9.7.x86_64 : Common files for the SSSD
Repo : rhel-7-server-rpms
Matched from:
Filename : /usr/sbin/sssd
#
and installing sssd-common package, no "sssd" package is present, shouldn't we change
packages = ('sssd',)
to:
packages = ('sssd', 'sssd-common')
in sos/plugins/sssd.py#L21 ?
Could somebody with sssd packaging knowledge confirm, if the above test is precise detection of SSSD functionality/feature present on a system?
Raising needinfo on the reporter, to validate if "sssd-common" is the right (and the only relevant) package to be added to the test to automatically enable sssd plugin.
Hi Maria,
question which Pavel asked. Currently is sssd details collected by sosreport when "sssd" package is present as per
https://github.com/sosreport/sos/blob/master/sos/report/plugins/sssd.py#L22
And all sosreport you shared does not have package sssd which means sosreport will not run sssd plugin.
Question was if we should run sssd plugin with different conditions for example if "sssd-common" package is installed or with any other package?
Same as for other plugins we will not collect everything every time, so we need to know conditions when to collect sssd related data.
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/RHBA-2021:2804