Bug 1708275
| Summary: | dyndns_update = True is no longer enough to get the IP address of the machine updated in IPA upon sssd.service startup | |||
|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Jan Pazdziora (Red Hat) <jpazdziora> | |
| Component: | sssd | Assignee: | Tomas Halman <thalman> | |
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | |
| Severity: | unspecified | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | 30 | CC: | abokovoy, jhrozek, jpazdziora, lslebodn, mzidek, pbrezina, rharwood, sbose, ssorce, thalman | |
| Target Milestone: | --- | |||
| Target Release: | --- | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | ||
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1736861 (view as bug list) | Environment: | ||
| Last Closed: | 2020-05-26 14:30: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: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 1736861 | |||
Alexander is right. This issue affects AD DNS updates as well. Upstream ticket: https://pagure.io/SSSD/sssd/issue/4047 Fixed the double negative in the summary/title. (In reply to Jan Pazdziora from comment #3) > Fixed the double negative in the summary/title. We don't need no education :-) * master: * f2c69a6 * 1c75218 * 5b235bb This message is a reminder that Fedora 29 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '29'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 29 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. This message is a reminder that Fedora 30 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '30'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 30 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Hello Pavel, seeing https://github.com/SSSD/sssd/issues/5015 was closed with milestone SSSD 2.3, is it safe to assume that the issue is still present in Fedora and thus the version should be changed to 31, to avoid letting this bugzilla slip to EOL? Fedora 30 changed to end-of-life (EOL) status on 2020-05-26. Fedora 30 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |
Description of problem: Man sssd-ipa(5) says dyndns_refresh_interval (integer) How often should the back end perform periodic DNS update in addition to the automatic update performed when the back end goes online. This option is optional and applicable only when dyndns_update is true. Default: 0 (disabled) suggesting that even when this option is not set (the default), when dyndns_update = True is set, the IP address update in DNS should happen upon backend going online, meaning during systemctl start sssd.service. That does not seem to be happening. Version-Release number of selected component (if applicable): sssd-ipa-2.1.0-2.fc29.x86_64 How reproducible: Deterministic. Steps to Reproduce: 1. I'm running this in container which makes it easy for me to change IP address. 2. On the (future) IPA client machine, run ipa-client-install with --enable-dns-updates 3. Observe that the IP address got set in DNS. 4. Change the IP address of the IPA client machine. 5. Run systemctl restart sssd.service. 6. Check the IP address of the IPA client machine in IPA server's DNS. Actual results: Old IP address. Expected results: New IP address. Additional info: In the log, I see [ipa_init_dyndns] (0x0100): Dynamic DNS updates are on. Checking for nsupdate... [ipa_init_dyndns] (0x0100): nsupdate is available [ipa_dyndns_init] (0x0040): Dyndns task can't be started, dyndns_refresh_interval is 0 [ipa_init_dyndns] (0x0080): Failure setting up automatic DNS update but no mention of the IP address getting updated. When I set dyndns_refresh_interval to non-zero value, I see the update refresh happening. Alexander suggests that the refactoring in https://github.com/SSSD/sssd/commit/df9e4802c060fc21d38f238265805092352e5c95 might not have covered the initial sync feature.