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 1917535 - sssd.conf man page: parameter dns_resolver_server_timeout and dns_resolver_op_timeout
Summary: sssd.conf man page: parameter dns_resolver_server_timeout and dns_resolver_op...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: sssd
Version: 8.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Iker Pedrosa
QA Contact: Dan Lavu
URL:
Whiteboard: sync-to-jira
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-01-18 16:50 UTC by Deepak Das
Modified: 2024-03-25 17:53 UTC (History)
9 users (show)

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

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2021:4435 0 None None None 2021-11-09 19:46:50 UTC

Description Deepak Das 2021-01-18 16:50:28 UTC 
Description of problem:

"man sssd-ad" has following entry "FAILOVER" in the failover section. 

-----------------------------------------------------------------------------
This section lists the available tunables. Please refer to their description in the sssd.conf(5), manual page.

       dns_resolver_server_timeout
           Time in milliseconds that sets how long would SSSD talk to a single DNS server before trying next one.

           Default: 1000

       dns_resolver_op_timeout
           Time in seconds to tell how long would SSSD try to resolve single DNS query (e.g. resolution of a hostname or an SRV
           record) before trying the next hostname or discovery domain.

           Default: 2

       dns_resolver_timeout
           How long would SSSD try to resolve a failover service. This service resolution internally might include several steps,
           such as resolving DNS SRV queries or locating the site.

           Default: 4
-----------------------------------------------------------------------------

As per above line the tunable parameter description should be present in "man sssd.conf" but base on check tunables "dns_resolver_server_timeout" and "dns_resolver_op_timeout" information is not present in "man sssd.conf".

Also when below error is observed, the man pages does not clarify under which section the parameter "dns_resolver_op_timeout" should be configured. 

----------------------------------------------------------------------------
 Attribute 'dns_resolver_op_timeout' is not allowed in section 'domain/ter.teradyne.com'. Check for typos
----------------------------------------------------------------------------


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

sssd-2.3.0-9.el8.x86_64

How reproducible:

Always

Steps to Reproduce:
1.
2.
3.

Actual results:

As per "man sssd-ad" the tuneables parameter "dns_resolver_server_timeout" and "dns_resolver_op_timeout" are not present in "man sssd.conf".

Expected results:

The tunables should be mentioned in "man sssd.conf" and under which section it should be possible to configure them.

Additional info:
Comment 4 Iker Pedrosa 2021-04-29 15:33:59 UTC 
Upstream ticket:
https://github.com/SSSD/sssd/issues/5616
Comment 5 Pavel Březina 2021-05-24 16:06:00 UTC 
Pushed PR: https://github.com/SSSD/sssd/pull/5645

* `master`
    * 7190f6b5d5b523e18e8c320df73c44b082c4d99b - SSSD man: man_dns_resolver_parameter_modification
    * 43b9b0922aa24a03ea466c673646d5e3079403fe - SSSD man: man_dns_resolver_parameter_modification
Comment 8 Dan Lavu 2021-06-14 23:08:12 UTC 
Verified against sssd-2.5.1-1.el8.x86_64

man sssd.conf contains the following 


       dns_resolver_server_timeout (integer)
           Defines the amount of time (in milliseconds) SSSD would try to talk to DNS server before trying next DNS server.

           Please see the section “FAILOVER” for more information about the service resolution.

           Default: 1000

       dns_resolver_op_timeout (integer)
           Defines the amount of time (in seconds) to wait to resolve single DNS query (e.g. resolution of a hostname or an SRV record) before try next hostname or DNS
           discovery.

           Please see the section “FAILOVER” for more information about the service resolution.

           Default: 3
Comment 14 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
Note You need to log in before you can comment on or make changes to this bug.