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.
DescriptionNikolai Kondrashov
2014-01-17 13:02:23 UTC
Description of problem:
If sssd AD or IPA provider has dyndns_refresh_interval specified as less than 60 seconds, actual refresh interval will be 60 seconds regardless.
This is because of the update rate limit hard-coded in ad_dyndns_update_send and ipa_dyndns_update_send.
Version-Release number of selected component (if applicable):
python-sssdconfig-1.11.2-24.el7.noarch
sssd-krb5-1.11.2-24.el7.x86_64
sssd-krb5-common-1.11.2-24.el7.x86_64
sssd-tools-1.11.2-24.el7.x86_64
sssd-common-1.11.2-24.el7.x86_64
sssd-ad-1.11.2-24.el7.x86_64
sssd-1.11.2-24.el7.x86_64
sssd-client-1.11.2-24.el7.x86_64
sssd-ipa-1.11.2-24.el7.x86_64
sssd-proxy-1.11.2-24.el7.x86_64
sssd-common-pac-1.11.2-24.el7.x86_64
sssd-ldap-1.11.2-24.el7.x86_64
How reproducible:
Always
Steps to Reproduce:
1. Assign an address to a dummy interface.
2. Configure sssd for dynamic DNS updates either with AD or IPA provider.
3. Specify the dummy interface with dyndns_iface.
4. Specify 10 second refresh interval with dyndns_refresh_interval.
5. Start sssd.
6. Wait for initial dynamic DNS update.
7. Change the dummy interface address.
8. Wait 10 seconds.
9. Check if the DNS records correspond to the interface address.
10. Wait 50 seconds.
11. Check if the DNS records correspond to the interface address.
Actual results:
First check: DNS records are outdated.
Second check: DNS records are up-to-date.
Expected results:
First check: DNS records are up-to-date.
Second check: DNS records are up-to-date.
Additional info:
It would suffice to specify this limit in the documentation, but a better fix would be making refresh interval less than 60 seconds effective, while preserving the 60 seconds limit for longer intervals.
Thank you for the bug report. I'm proposing the bug for 7.1, though, we're close to the 7.0 deadline and I don't want to bring in too many fixes unless needed.
Thank you taking your time and submitting this request for Red Hat Enterprise Linux. Unfortunately, this bug was not given a priority and was deferred both in the upstream project and in Red Hat Enterprise Linux.
Given that we are unable to fulfill this request in following Red Hat Enterprise Linux releases, I am closing the Bugzilla as DEFERRED. To request that Red Hat re-considers the decision, please re-open the Bugzilla via appropriate support channels and provide additional business and/or technical details about its importance to you.
Note that you can still track this request or even contribute patches in the referred upstream Trac ticket.