SSSD / sssd

#756 Service discovery fails when going back online
Closed: Fixed Opened by sbose.

Closed: Fixed
Reopen Issue

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.

Fields changed

status: new => assigned

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.5.1

Fixed by 7daf6c9f7a0e583a1ba033bb858208b51358bf2f and 0b586311f6a077deba5f43ca85a8536bfd203c66

resolution: => fixed
status: assigned => closed

Fields changed

rhbz: => 0

Metadata Update from @sbose:
- Issue assigned to sbose
- Issue set to the milestone: SSSD 1.5.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:
- https://github.com/SSSD/sssd/issues/1798

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.
Metadata
None
None
None
Normal
defect
Failover
1.5.0
0
0
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.