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 1632159 - sssd-kcm starts successfully for non existent socket_path
Summary: sssd-kcm starts successfully for non existent socket_path
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: sssd
Version: 8.0
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: rc
: 8.0
Assignee: Iker Pedrosa
QA Contact: Madhuri
URL:
Whiteboard: sync-to-jira
Depends On: 1682305
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-09-24 09:08 UTC by Niranjan Mallapadi Raghavender
Modified: 2021-11-10 09:01 UTC (History)
14 users (show)

Fixed In Version: sssd-2.5.0-1.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-11-09 19:46:33 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github SSSD sssd issues 5406 0 None open sssd-kcm starts successfully for non existent socket_path 2021-02-17 09:23:25 UTC
Red Hat Product Errata RHBA-2021:4435 0 None None None 2021-11-09 19:46:53 UTC

Comment 8 Iker Pedrosa 2020-11-12 09:40:53 UTC 
@mniranja and @atikhono can you tell me which is the expected behaviour for this bugzilla from the following statements? By the way, more than one can be selected.
1- Socket path is not defined in sssd configuration, socket location fall backs to the default one and logs don't warn about it. Socket is opened and sssd-kcm starts successfully.
2- Socket path is not defined in sssd configuration, socket location fall backs to the default one and logs warn about it. Socket is opened and sssd-kcm starts successfully.
3- Socket path is defined in a valid location. Socket is opened and sssd-kcm starts successfully.
4- Socket path is defined in an invalid location. Socket is not opened and sssd-kcm fails while starting.
5- Socket path is defined in an invalid location. Socket creation fall backs to the default location (/var/run/.heim_org.h5l.kcm-socket) and sssd-kcm starts successfully.

Those are the ideas that come to my mind but more can be added.
Comment 10 Alexey Tikhonov 2020-11-12 17:13:02 UTC 
I would propose: 

 - "Socket path is not defined in sssd configuration" => fall backs to the default and log SSSDBG_CONF_SETTINGS

 - "Socket path is defined in a valid location" => log SSSDBG_CONF_SETTINGS

 - "Socket path is defined in an invalid location" => log SSSDBG_CRIT_FAILURE + log journal message and fall back to default (log message should indicate fall back to default)
Comment 11 Iker Pedrosa 2020-11-17 13:37:53 UTC 
Upstream ticket:
https://github.com/SSSD/sssd/issues/5406
Comment 21 Pavel Březina 2021-02-19 13:29:47 UTC 
Pushed PR: https://github.com/SSSD/sssd/pull/5407

* `master`
    * f890fc4b592767f3f0b2bd5515cbd9516505ebe9 - RESPONDER: check that configured sockets match
Comment 29 errata-xmlrpc 2021-11-09 19:46:33 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 (sssd 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:4435
Note You need to log in before you can comment on or make changes to this bug.