You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
Cloned from Pagure issue: https://pagure.io/SSSD/sssd/issue/1926
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.
Comments
Comment from dpal at 2013-05-16 15:37:08
Fields changed
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
Comment from jhrozek at 2013-09-16 10:51:24
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]
Comment from dpal at 2014-09-26 18:49:57
Fields changed
mark: => 0
Comment from jhrozek at 2015-02-10 15:17:12
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..
changelog: =>
priority: major => minor
Comment from jhrozek at 2015-02-12 11:44:32
Fields changed
blocking: => 2558
Comment from preichl at 2015-06-18 15:49:24
Fields changed
owner: somebody => preichl
sensitive: => 0
Comment from preichl at 2015-07-28 17:15:34
Fields changed
patch: 0 => 1
Comment from preichl at 2015-08-20 14:31:02
Fields changed
resolution: => fixed
status: new => closed
Comment from jhrozek at 2017-02-24 14:56:03
Metadata Update from @jhrozek:
The text was updated successfully, but these errors were encountered: