-
Epic
-
Resolution: Done
-
Normal
-
None
-
None
-
Upgrade Quickstarts Service databases' to 16.4
-
False
-
-
False
-
Unset
-
In Progress
-
0% To Do, 0% In Progress, 100% Done
-
-
Description
Defines the work to be done to upgrade the Quickstarts stage and production databases to the consolidated version 16.4.
Chosen upgrade path
- Quickstarts is currently running RDS 13.14
- 13.14 --> 13.16
- 13.16 --> 16.4
The reason for this is that after asking to the AWS customer support —RHCLOUD-38615—, we got told that even though their "Choosing a major version for an RDS PostgreSQL upgrade" document shows that in theory we could do one less jump, the reality is that the Blue/Green RDS upgrades do not allow major version jumps when they're one more than one version apart.
App-sre IC has indicated multiple versions is supported and encouraged by AWS after upgrading a minor version first to open the range: https://redhat-internal.slack.com/archives/CCRND57FW/p1742806964278039?thread_ts=1742547198.424619&cid=CCRND57FW
Useful resources
- AWS - Log in to the console.
- AWS - Choosing a major version for an RDS PostgreSQL upgrade.
- AppInterface — Upgrade Major Version for PostgreSQL RDS instance.
Announcements to be made for the production upgrade
| Ticket | Task | Email thread/Merge request | Is it done? Is it merged? |
|---|---|---|---|
| N/A | Announce the upgrade via email two weeks in advance | ||
| Set up a Pendo preemptive alert announcing the upgrade in two weeks and schedule another one for the day of the upgrade | |||
| Set up the maintenance announcement in the status page | |||
| Send a preemptive Slack message to the relevant channels | |||
| Send a Slack message to the relevant channels once the maintenance is taking place | |||
| Send a Slack message to the relevant channels once the maintenance is over |
Work to be done by engineers for the stage upgrade
| Ticket | Order | Task | MRs |
|---|---|---|---|
| Before anything else | Check that no replication slots are being used. | ||
| Any time before the upgrade | Review the minor version upgrade's database settings and parameters for version 13.16. | ||
| Any time before the upgrade | Create the major version upgrade's database settings and parameters for version 16.4. | ||
| Any time before the upgrade | Add the logical replication setting to the database's parameters. | ||
| Any time before the upgrade | Enable the Blue/Green upgrade settings | ||
| 1 | Specify the new database settings for the minor version upgrade to 13.16. | ||
| 2 | Wait for the database to be upgraded. | ||
| 3 | Specify the new database settings for the major version upgrade to 16.4 | ||
| 4 | Wait for the database to be upgraded. | ||
| 7 | Run the post-upgrade maintenance scripts in the database. | ||
| 8 | Clean up the old database configuration files. |
Work to be done by engineers for the production upgrade
| Ticket | Order | Task | MRs |
|---|---|---|---|
| Before anything else | Check that no replication slots are being used. | ||
| Any time before the upgrade | Review the minor version upgrade's database settings and parameters for version 13.16. | ||
| Any time before the upgrade | Create the major version upgrade's database settings and parameters for version 16.4. | ||
| Any time before the upgrade | Add the logical replication setting to the database's parameters. | ||
| Any time before the upgrade | Enable the Blue/Green upgrade settings | ||
| 1 | Specify the new database settings for the minor version upgrade to 13.16. | ||
| 2 | Wait for the database to be upgraded. | ||
| 3 | Specify the new database settings for the major version upgrade to 16.4 | ||
| 4 | Wait for the database to be upgraded. | ||
| 7 | Run the post-upgrade maintenance scripts in the database. | ||
| 8 | Clean up the old database configuration files. |
- is related to
-
-
- Closed
-