#1484 failover should protect against empty host names
Closed: Fixed None Opened 7 years ago by jhrozek.

I encountered a setup where the KDCs were separated with a double comma and effectively an empty host name was added to the fail over list, which created spurious error messages during failover.

This is wrong configuration, but because the servers can be retrieved from DNS using a SRV query, too, we should make sure we only add valid host names to the fail over list.


Fields changed

description: I encountered a setup where the KDCs were separated with a double comma and effectively an empty host name was added to the fail over list, which created spurious error messages during failover.

This is wrong configuration, but because the servers can be retrieved from DNS, too, we should make sure we only add valid host names to the fail over list. => I encountered a setup where the KDCs were separated with a double comma and effectively an empty host name was added to the fail over list, which created spurious error messages during failover.

This is wrong configuration, but because the servers can be retrieved from DNS using a SRV query, too, we should make sure we only add valid host names to the fail over list.

Fields changed

milestone: NEEDS_TRIAGE => Temp milestone
proposed_priority: Undefined => Nice to have
rhbz: => todo

Moving all the features planned for 1.10 release into 1.10 beta.

milestone: Temp milestone => SSSD 1.10 beta

Fields changed

owner: somebody => mzidek

Fields changed

patch: 0 => 1
status: new => assigned

Fields changed

selected: => Not need

Moving tickets that are not a priority for SSSD 1.10 into the next release.

milestone: SSSD 1.10 beta => SSSD 1.11 beta

There was actually a patch on the list for quite some time, that got reviewed a while ago, but only pushed today.

Fixed in 04759b5

design: =>
design_review: => 0
fedora_test_page: =>
milestone: SSSD 1.11 beta => SSSD 1.10 beta
resolution: => fixed
status: assigned => closed

Metadata Update from @jhrozek:
- Issue assigned to mzidek
- Issue set to the milestone: SSSD 1.10 beta

3 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/2526

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