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

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 7daf6c9 and 0b58631

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

7 years ago

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.

Login to comment on this ticket.

Metadata