Bug 2115171

Summary: SSSD: duplicate dns_resolver_* option in man sssd.conf
Product: Red Hat Enterprise Linux 9 Reporter: Sunny Wu <suwu>
Component: sssdAssignee: jstephen
Status: CLOSED ERRATA QA Contact: shridhar <sgadekar>
Severity: low Docs Contact:
Priority: unspecified    
Version: 9.1CC: aboscatt, atikhono, pasik, pbrezina
Target Milestone: rcKeywords: Triaged
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard: sync-to-jira
Fixed In Version: sssd-2.8.1-1.el9 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-05-09 08:19:51 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 Sunny Wu 2022-08-04 02:42:04 UTC 
Description of problem:

In "man sssd.conf", dns_resolver_server_timeout and dns_resolver_op_timeout options are printed twice:

~~~
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.

   The AD provider will use this option for the CLDAP ping timeouts as
   well.

   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

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
~~~

Looks like the change was introduced by:

https://github.com/SSSD/sssd/commit/7190f6b5d5b523e18e8c320df73c44b082c4d99b
https://github.com/SSSD/sssd/commit/43b9b0922aa24a03ea466c673646d5e3079403fe

Version-Release number of selected component (if applicable):
# rpm -qa | grep sssd | sort
python3-sssdconfig-2.6.2-4.el8_6.1.noarch
sssd-ad-2.6.2-4.el8_6.1.x86_64
sssd-client-2.6.2-4.el8_6.1.x86_64
sssd-common-2.6.2-4.el8_6.1.x86_64
sssd-common-pac-2.6.2-4.el8_6.1.x86_64
sssd-dbus-2.6.2-4.el8_6.1.x86_64
sssd-ipa-2.6.2-4.el8_6.1.x86_64
sssd-kcm-2.6.2-4.el8_6.1.x86_64
sssd-krb5-common-2.6.2-4.el8_6.1.x86_64
sssd-nfs-idmap-2.6.2-4.el8_6.1.x86_64
sssd-tools-2.6.2-4.el8_6.1.x86_64
sssd-winbind-idmap-2.6.2-4.el8_6.1.x86_64

How reproducible:
100%

Steps to Reproduce:
1. man sssd.conf
2. search "dns_resolver"
Comment 1 Sunny Wu 2022-08-04 08:08:12 UTC 
Seems not entirely the same.

An extra paragraph in the first occurrence:

dns_resolver_server_timeout (integer)

<...>

   The AD provider will use this option for the CLDAP ping timeouts as
   well.
Comment 2 jstephen 2022-08-17 20:33:19 UTC 
Upstream PR: https://github.com/SSSD/sssd/pull/6309
Comment 3 Alexey Tikhonov 2022-09-23 12:24:35 UTC 
Pushed PR: https://github.com/SSSD/sssd/pull/6309

* `master`
    * a2417753dfe612b09dfaa72e2c30ddabbc205a24 - MAN: Remove duplicate dns options
Comment 10 errata-xmlrpc 2023-05-09 08:19:51 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-2023:2514