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
If sssd goes from offline to online service discovery fails with "The status of SRV lookup is not resolved". During the check online operation all fail-over entries are reseted, but the service record entries are set to SRV_NOT_RESOLVED, which is an error state, instead of SRV_NEUTRAL.
I would make sense to rename SRV_NOT_RESOLVED to SRV_RESOLVE_ERROR to avoid misuse in future.
Cloned from Pagure issue: https://pagure.io/SSSD/sssd/issue/756
If sssd goes from offline to online service discovery fails with "The status of SRV lookup is not resolved". During the check online operation all fail-over entries are reseted, but the service record entries are set to SRV_NOT_RESOLVED, which is an error state, instead of SRV_NEUTRAL.
I would make sense to rename SRV_NOT_RESOLVED to SRV_RESOLVE_ERROR to avoid misuse in future.
Comments
Comment from sbose at 2011-01-04 11:58:04
Fields changed
status: new => assigned
Comment from sgallagh at 2011-01-04 15:00:55
Fields changed
milestone: NEEDS_TRIAGE => SSSD 1.5.1
Comment from sbose at 2011-01-07 09:49:00
Fixed by 7daf6c9 and 0b58631
resolution: => fixed
status: assigned => closed
Comment from dpal at 2012-01-19 03:03:04
Fields changed
rhbz: => 0
Comment from sbose at 2017-02-24 14:38:20
Metadata Update from @sbose:
The text was updated successfully, but these errors were encountered: