#2282 Forcing IPA clients to prioritise different IPA Servers
Closed: Fixed None Opened 11 years ago by shelltoesuperstar.

Could a "--primary" flag be added to the ipa-client-install script? It could behave in the same way as the "--server" flag and be a substitute for it but it would force all enrolment comms to be kept to the named server and reorder the ipa_server entry in sssd.conf from {{{"ipa_server = srv, x.x.x.x"}}} to {{{"ipa_server = x.x.x.x, srv"}}}


A note from the SSSD team:

There's some work in the planning stages to support "primary" servers in sssd, so that if ot fails over to another server in the list, it will try to fail back to the primary if it comes back to life. Right now it always hang on to the last server that worked.

There are a few possible scenarios:

  1. client install, --fixed-primary is passed. This causes the discovered or user-provided (either via input or --server) server as the first value in the ipa_server directive in sssd.conf.

  2. client install, --fixed-primary is not passed. srv is first in the ipa_server directive

  3. server install, there is no --fixed-primary option. The only server listed is the IPA server itself.

Metadata Update from @shelltoesuperstar:
- Issue assigned to rcritten
- Issue set to the milestone: FreeIPA 3.0 Beta 1

6 years ago

Login to comment on this ticket.

Metadata