| Summary: | Update/Upgrade process needs to be addressed and documented for any zStream errata and for next release | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Jenny Severance <jgalipea> |
| Component: | doc-Identity_Management_Guide | Assignee: | Deon Ballard <dlackey> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | ecs-bugs |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 6.3 | CC: | dpal, jskeoch, mkosek, rcritten |
| Target Milestone: | rc | Keywords: | Documentation |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-06-21 23:17:46 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Bug Depends On: | |||
| Bug Blocks: | 736854 | ||
|
Description
Jenny Severance
2011-12-12 15:03:55 UTC
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. |