Hide Forgot
Description of problem: The process for yum update and upgrading to the next IPA server release needs to be addressed and documented. Like "Does it / Should it require an 'ipactl restart'"? Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Pick one of your masters. # yum update ipa-server This in itself will update this IPA server instance Restart of IPA services should be automatic Schema upgrade should be automatic It may take a minute to apply the package update while changes are applied Enrolled clients do not need new packages installed. The only thing it might do is pull in any new dependencies, but it won't otherwise change enrollment. So, for example, it might pull in an updated certmonger that has fixes. You can upgrade masters one at a time but new features will not be available on those masters not upgraded yet. The updated schema will appear on all masters, updated or not. Our expectation is that customers will upgrade servers within a relatively short timeframe (not weeks). It does not however, need to be a tightly coordinated "ok, every press enter...NOW" sort of affair.
Closing.