Controlled patch management with Red Hat Satellite content views
Author: DEWOLF.IT
Diagnose the Satellite content chain and promote reproducible content view versions through lifecycle environments.
This English edition covers the main steps. See the Dutch article for the full detail and examples.
Follow the content chain
Content flows from synchronised repositories through published content view versions into lifecycle environments. A host also needs the right registration, repository access and applicable package architecture. Synchronising a repository alone does not make its update available to a production host.
Publish and promote a defined version
Identify the repositories, filters, CVEs and applications in scope. Publish a candidate, validate it in the appropriate test environment, and promote that same version through acceptance to production. Record the composite components if you use a composite content view.
Trace missing content layer by layer
- Verify repository synchronisation and that the exact package or advisory is present.
- Inspect content view filters, the published version and its promotion.
- Confirm the host's lifecycle environment, content view and enabled repositories.
- Check architecture, release constraints, dependencies and Capsule sync where applicable.
Define acceptance and recovery
Verify patch levels and application health, and plan recovery for installed packages and data. Reassigning content alone does not roll back packages already installed.
See the Red Hat Satellite documentation for your version.
