Bug 1917444

Summary:	SSSD Error Msg Improvement: Server resolution failed: [2]: No such file or directory
Product:	Red Hat Enterprise Linux 8	Reporter:	Deepak Das <ddas>
Component:	sssd	Assignee:	Iker Pedrosa <ipedrosa>
Status:	CLOSED ERRATA	QA Contact:	Anuj Borah <aborah>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	8.3	CC:	atikhono, dlavu, grajaiya, ipedrosa, jhrozek, kbanerje, lslebodn, mzidek, pbrezina, thalman, tscherf
Target Milestone:	rc	Keywords:	Triaged
Target Release:	---	Flags:	pm-rhel: mirror+
Hardware:	x86_64
OS:	Linux
Whiteboard:	sync-to-jira
Fixed In Version:	sssd-2.5.1-1.el8	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-11-09 19:46:34 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Deepak Das 2021-01-18 13:55:19 UTC

Description of problem:

SSSD debug log snip following message is observed in support case 02835160 following. 

----------------------------------------------------------------------------
(2020-12-31 11:19:39): [be[example.com]] [fo_resolve_service_send] (0x0100): Trying to resolve service 'AD'
(2020-12-31 11:19:39): [be[example.com]] [get_server_status] (0x1000): Status of server 'ad-dc3.example.com' is 'name resolved'
(2020-12-31 11:19:39): [be[example.com]] [fo_resolve_service_activate_timeout] (0x2000): Resolve timeout set to 6 seconds
(2020-12-31 11:19:39): [be[example.com]] [resolve_srv_send] (0x0200): The status of SRV lookup is resolved
(2020-12-31 11:19:39): [be[example.com]] [get_server_status] (0x1000): Status of server 'ad-dc3.example.com' is 'name resolved'
(2020-12-31 11:19:39): [be[example.com]] [be_resolve_server_process] (0x0040): The fail over cycled through all available servers
(2020-12-31 11:19:39): [be[example.com]] [be_resolve_server_done] (0x1000): Server resolution failed: [2]: No such file or directory
(2020-12-31 11:19:39): [be[example.com]] [be_mark_dom_offline] (0x1000): Marking back end offline
(2020-12-31 11:19:39): [be[example.com]] [be_mark_offline] (0x2000): Going offline!
----------------------------------------------------------------------------

As per above error message, when "Server resolution failed" is observed it also adds  "No such file or directory" which is not clear as to which file or directory SSSD is referring to if any.

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

sssd-2.3.0-9.el8.x86_64

How reproducible:

Always.

Actual results:
 
Message "No such file or directory" is confusing.

Expected results:

Message "No such file or directory" should not be displayed if the message is false positive.

Additional info:

The object of this bugzilla is to request improvement of SSSD debug messages to make it more customer friendly.

Comment 7 Iker Pedrosa 2021-04-29 15:33:15 UTC

Upstream ticket:
https://github.com/SSSD/sssd/issues/5614

Comment 8 Alexey Tikhonov 2021-05-31 13:16:53 UTC

Pushed PR: https://github.com/SSSD/sssd/pull/5622

* `master`
    * 9c06088de65630f7407d505e015643fa656803d9 - SSSD Log: no_such_file_or_directory_modification

Comment 23 errata-xmlrpc 2021-11-09 19:46:34 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