Learn more about these different git repos.
Other Git URLs
Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 7): Bug 1056526
Description of problem: Sssd AD (and probably IPA) provider's failing dynamic DNS updates are not retried, another update attempt is only done after refresh interval. With default refresh interval, a failed update means than new or changed host DNS records wouldn't be created for at least another 24 hours. Version-Release number of selected component (if applicable): 1.11.2-29.el7.x86_64 How reproducible: Always.
Fields changed
blockedby: => blocking: => changelog: => coverity: => design: => design_review: => 0 feature_milestone: => fedora_test_page: => milestone: NEEDS_TRIAGE => SSSD 1.12 beta review: True => 0 selected: => testsupdated: => 0
owner: somebody => preichl
Bring back if we have reports about dyndns being unstable.
milestone: SSSD 1.12 beta => SSSD 1.14 beta
mark: => 0 priority: major => minor sensitive: => 0
I think this can be deferred, we haven't seen any bug reports about dyndns being unstable..
milestone: SSSD 1.14 beta => SSSD Deferred
I don't see the point, really. I suggest we close this ticket.
review: 0 => 1
Pasting the discussion from the bugzilla into this ticket to keep the info in upstream:
Petr Spacek 2014-01-23 06:05:27 EST Note for potential implementation - http://tools.ietf.org/html/rfc1536#section-1 : [...] Both name servers and stub resolvers should, therefore, implement some kind of a retransmission policy based on round trip time estimates of the name servers. The client should back-off exponentially, probably to a maximum timeout value. [...] Comment 3 Nikolai Kondrashov 2014-01-23 06:21:15 EST Note that nsupdate, by default, seem to do 3 attempts to do the update, with 3 seconds in between. So, sssd shouldn't do it, but indeed some exponential retry scheme might be used instead. Comment 4 Petr Spacek 2014-01-23 06:34:45 EST I'm not against three successive attempts with timeout = 3 seconds but then the timeout raise exponentially.
Since nobody complained for several years, we can close this ticket.
resolution: => wontfix status: new => closed
Metadata Update from @jhrozek: - Issue assigned to preichl - Issue set to the milestone: SSSD Patches welcome
SSSD is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in SSSD's github repository.
This issue has been cloned to Github and is available here: - https://github.com/SSSD/sssd/issues/3248
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Login to comment on this ticket.