Ensure all services (candlepin, pulp, foreman_tasks) return "ok" and the database latencies are under 50ms.

Your Satellite server is useless if your Capsules (Smart Proxies) are mismatched.

The upgrade process follows a strict sequence. Deviating from this order breaks dependency chains.

To reduce "upgrade anxiety," 6.17 includes enhanced integration and pre-flight checks.

For questions or to schedule your upgrade, contact the Infrastructure Team.

This introduces specific dependencies:

Once the main server is stable, upgrade each Capsule separately. You can use the Capsule Upgrade Playbook from the Satellite UI for remote execution. What’s New in 6.17? Upgrading connected Red Hat Satellite to 6.17