Closed AkshayGadhaveRH closed 1 month ago
The PR preview for aa0714ce00696094a2afdd7e3471c3ddb5591e8b is available at theforeman-foreman-documentation-preview-pr-3374.surge.sh
The following output files are affected by this PR:
@Lennonka agreed. Makes sense to me.
I've set both "review done" labels because it's correct that PG 13 is needed for 3.12/6.16 and I have reviewed the style as well.
I don't think it's a good idea to set tech review done
without an actual technical review. This is a new feature that deserves a closer look from Engineering. Also, the latest comment in https://issues.redhat.com/browse/SAT-28273 suggests that there is additional context to consider. I'm unsetting the tech review done
label again. (IMHO docs people should not provide tech review for significant updates or new features, that's why we have two separate types of review.)
@AkshayGadhaveRH please work with the Platform team to secure a proper technical review.
@evgeni does this plan look good? (also, small question for you)
Will this involve creating backup of old (pgsql12 + RHEL 8) and restoring that on fresh (pgsql13 + EL8)?
_Edit existing
proc_upgrading-the-external-database.adoc
module._
Looks good to me.
@evgeni Do we have a technical ack?
@Lennonka @evgeni is this good to go?
Merged to "master" and cherry-picked:
proc_upgrading-a-connected-project-server.adoc
)
The external database should be upgraded from PostgreSQL 12 to 13. Mentioning this in the ext DB upgrade chapter.
JIRA: https://issues.redhat.com/browse/SAT-28273
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.)
Checklists
Please cherry-pick my commits into: