Create new swh db for the swh-next-version instance

This would allow to test migration ahead of actual deployments. But without actually deploying the staging instance (if something is wrong for example).

plan:

• swh-site/swh-private-data: create db on db1.staging
• Dump (pg_dump) the db1.staging swh-web instance
• Restore the dump on the new swh-web-next-version db instance
• k8s-private-data: adapt the secrets to reference the access credentials
• Adapt the chart to use that new instance
• Fix permission issue

changed milestone to %MRO 2023

added Web app activity::Deployment labels

mentioned in merge request swh/infra/ci-cd/swh-charts!175 (merged)

changed the description

mentioned in commit swh/infra/puppet/puppet-swh-private-data-censored@878f4dfc

mentioned in commit swh/infra/puppet/puppet-swh-site@9541618a

marked the checklist item swh-site/swh-private-data: create db on db1.staging as completed

marked the checklist item Dump (pg_dump) the db1.staging swh-web instance as completed

marked the checklist item Restore the dump on the new swh-web-next-version db instance as completed

mentioned in commit swh/infra/ci-cd/swh-charts@f7a4fcf3

marked the checklist item k8s-private-data: adapt the secrets to reference the access credentials as completed

changed the description

changed the description

Running in circle currently, i'm able to set the password from the psql command [1] (and then i can connect to the db from my machine or elsewhere). If I make the puppet agent run, it just resets the password (supposedly the right password according to notice output [2]) but then i can't log anymore

Either way, i can connect with the guest user though.

[1]

postgres=# ALTER USER "swh-web" WITH ENCRYPTED PASSWORD '<redacted-clear-pass-properly-referneced-in-private-data-and-so-the-debug-log-confirms-it>';
ALTER ROLE

[2]

Notice: type: webapp-next-version name: swh-web-next-version, user: swh-web, password: redacted-by-me-plain-good-pass
Notice: /Stage[main]/Profile::Postgresql::Server/Notify[Debug log for db webapp-next-version]/message: defined 'message' as 'type: webapp-next-version name: swh-web-next-version, user: swh-web, password: redacted-by-me-plain-good-pass'
Notice: /Stage[main]/Profile::Postgresql::Server/Postgresql::Server::Db[swh-web]/Postgresql::Server::Role[swh-web]/Postgresql_psql[ALTER ROLE swh-web ENCRYPTED PASSWORD ****]/command: changed [redacted-by-puppet] to [redacted-by-puppet]

d'oh, of course, that won't work... ok, i know what to do.

know what to do

Use different user/pass accounts. Done.

mentioned in commit swh/infra/puppet/puppet-swh-site@61336dcf

changed the description

mentioned in commit swh/infra/ci-cd/swh-charts@de61b8a7

marked the checklist item Adapt the chart to use that new instance as completed

changed the description

marked the checklist item Fix permission issue as completed

From a recent new swh-web release which trigger the webapp running in swh-cassandra-next-version (nothing to do but the migration performed nonetheless without any sort of issue)

Operations to perform:
  Apply all migrations: admin, auth, contenttypes, sessions, swh_web_add_forge_now, swh_web_auth, swh_web_mailmap, swh_web_save_code_now
Running migrations:
  No migrations to apply.
Stream closed EOF for swh-cassandra-next-version/web-56f4d89f9b-lhbvj (do-migration)

closed