Learn more about these different git repos.
Other Git URLs
Currently the DNS updates are run after the SSSD goes online for the first time. But it would help in enroll scenarios if the update was run after the SSSD is run for the first time.
We already do something very similar for the SUDO updates and to some extent with enumerations.
milestone: NEEDS_TRIAGE => SSSD 1.12 beta
rhbz: => todo
summary: RFE: Start the dynamic DNS update after the SSSD has been setup for the first time => [RFE] Start the dynamic DNS update after the SSSD has been setup for the first time
type: defect => enhancement
Linked to Bugzilla bug: https://bugzilla.redhat.com/show_bug.cgi?id=1007968 (Red Hat Enterprise Linux 7)
rhbz: todo => [https://bugzilla.redhat.com/show_bug.cgi?id=1007968 1007968]
mark: => 0
There are already dyndns tickets in 1.13 beta such as #2549 it makes sense to reconsider this ticket in that scope as well.
Chances are the update-on-online-callback functionality already does what we need, but we should test it..
priority: major => minor
blocking: => 2558
owner: somebody => preichl
sensitive: => 0
patch: 0 => 1
resolution: => fixed
status: new => closed
Metadata Update from @jhrozek:
- Issue assigned to preichl
- Issue marked as blocked by: #2558
- Issue set to the milestone: SSSD 1.13.1
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:
If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.
Thank you for understanding. We apologize for all inconvenience.
to comment on this ticket.