Skip to content

Conversation

@AkshayGadhaveRH
Copy link
Contributor

Existing documentation points to the RHEL docs for steps to upgrade external DB. However, some steps need to be tweaked.

JIRA:
https://issues.redhat.com/browse/SAT-37171

What changes are you introducing?

Why are you introducing these changes? (Explanation, links to references, issues, etc.)

Anything else to add? (Considerations, potential downsides, alternative solutions you have explored, etc.)

Contributor checklists

  • I am okay with my commits getting squashed when you merge this PR.
  • I am familiar with the contributing guidelines.

Please cherry-pick my commits into:

  • Foreman 3.16/Katello 4.18 (Satellite 6.18)
  • Foreman 3.15/Katello 4.17
  • Foreman 3.14/Katello 4.16 (Satellite 6.17; orcharhino 7.4)
  • Foreman 3.13/Katello 4.15 (EL9 only)
  • Foreman 3.12/Katello 4.14 (Satellite 6.16; orcharhino 7.2 on EL9 only; orcharhino 7.3)
  • Foreman 3.11/Katello 4.13 (orcharhino 6.11 on EL8 only; orcharhino 7.0 on EL8+EL9; orcharhino 7.1 with Leapp)
  • Foreman 3.10/Katello 4.12
  • Foreman 3.9/Katello 4.11 (Satellite 6.15; orcharhino 6.8/6.9/6.10)
  • We do not accept PRs for Foreman older than 3.9.

@github-actions
Copy link

github-actions bot commented Oct 29, 2025

@Lennonka Lennonka added Needs tech review Requires a review from the technical perspective Needs style review Requires a review from docs style/grammar perspective Needs testing Requires functional testing labels Oct 29, 2025
Copy link
Contributor

@Lennonka Lennonka left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Minor tweaks :)

@pr-processor pr-processor bot added Waiting on contributor Requires an action from the author Needs re-review and removed Not yet reviewed Waiting on contributor Requires an action from the author labels Oct 29, 2025
Copy link
Contributor

@Lennonka Lennonka left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

SME review would be appreciated.

@Lennonka Lennonka added the Waiting on contributor Requires an action from the author label Oct 29, 2025
@pr-processor pr-processor bot added Needs re-review and removed Waiting on contributor Requires an action from the author Needs re-review labels Oct 29, 2025
@Lennonka Lennonka added tech review done No issues from the technical perspective and removed Needs tech review Requires a review from the technical perspective labels Oct 30, 2025
Copy link
Contributor

@Lennonka Lennonka left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM style wise

@Lennonka Lennonka added style review done No issues from docs style/grammar perspective and removed Needs style review Requires a review from docs style/grammar perspective labels Oct 30, 2025
@Lennonka
Copy link
Contributor

@AkshayGadhaveRH Since upgrade is a critical task, I would strongly prefer to have the new procedure tested by a QE.

Copy link
Contributor

@stejskalleos stejskalleos left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looking at the official RHEL 8 documentation, I see that the steps introduced here are duplicated; everything needed for the upgrade is already described in that documentation.

The procedure should be:

. Back up the `/var/lib/pgsql/data/postgresql.conf` and `/var/lib/pgsql/data/pg_hba.conf` files. (BTW, this step is mentioned in the el8 docs)
. Follow RHEL8 docs
. Make sure it's running.

@pr-processor pr-processor bot added the Waiting on contributor Requires an action from the author label Nov 4, 2025
Akshay Gadhave added 4 commits November 5, 2025 13:42
Existing documentation points to the RHEL docs for steps to upgrade external DB.
However, some steps need to be tweaked.

JIRA:
https://issues.redhat.com/browse/SAT-37171
@AkshayGadhaveRH AkshayGadhaveRH force-pushed the add-upgrading-external-postgres-12-to-13 branch from 7902608 to f491012 Compare November 5, 2025 08:16
@pr-processor pr-processor bot added Needs re-review and removed Waiting on contributor Requires an action from the author Needs re-review labels Nov 5, 2025
Copy link
Contributor

@stejskalleos stejskalleos left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tech ACK

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Needs testing Requires functional testing style review done No issues from docs style/grammar perspective tech review done No issues from the technical perspective

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants