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:
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/7190f6b5d5b523e18e8c320df73c44b082c4d99bhttps://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"
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.
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