-
Bug
-
Resolution: Done
-
Major
-
6.17.0
-
2
-
False
-
Sat_docs_6_2025, Satellite Endeavour Sprint 1
-
sat-endeavour
-
None
-
None
-
None
-
None
Description of problem:
The Satellite 6.17 upgrade guides : https://docs.redhat.com/en/documentation/red_hat_satellite/6.17/html-single/upgrading_connected_red_hat_satellite_to_6.17/index#Upgrading_satellite_upgrading-connected and https://docs.redhat.com/en/documentation/red_hat_satellite/6.17/html-single/upgrading_disconnected_red_hat_satellite_to_6.17/index#Upgrading_satellite_upgrading-connected
The documentation includes a step for upgrading PostgreSQL to version 13:
- "2.2. Upgrading a connected Satellite Server": 9. If you are using an external database, upgrade your database to PostgreSQL 13.
However, the upgrade to PostgreSQL was already a mandatory step in the upgrade procedure in the 6.16 upgrade guides. Because of this, users of Satellite 6.17 are already running PostgreSQL 13 and we can remove that step from the 6.17 upgrade guides.
How reproducible:
Is this issue a regression from an earlier version:
Steps to Reproduce:
1.
2.
3.
Actual behavior:
The upgrade guides include a step to upgrade to PostgreSQL 13.
Expected behavior:
The upgrade guides do not ask users to upgrade to PostgreSQL 13 because users already upgraded in the previous version.
Business Impact / Additional info: