v316: Release swh.counters v0.11.0
Merge request reports
Activity
assigned to @jenkins
added 4 commits
-
8e3e023f...7469fc74 - 3 commits from branch
staging - a87f3b4b - v312: Release swh.loader.cvs v0.8.3
-
8e3e023f...7469fc74 - 3 commits from branch
added 8 commits
-
1507ff2c...9ba772a7 - 6 commits from branch
staging - 8c201b69 - v312: Release swh.loader.cvs v0.8.3
- 31a837a3 - v314: Release swh.storage v2.4.1
-
1507ff2c...9ba772a7 - 6 commits from branch
added 1 commit
- 6b37e1bc - swh/next-next-version: Use the right url for the next-version counters
added 10 commits
-
d95098ea...4de61657 - 3 commits from branch
staging - b125c31c - v312: Release swh.loader.cvs v0.8.3
- 0abc7e67 - v314: Release swh.storage v2.4.1
- 88236e44 - v315: Release swh.loader.core v5.18.1
- 2518e051 - swh/next-next-version: Use the right url for the next-version counters
- 7737023b - v316: Release swh.counters v0.11.0
- c9f39624 - swh/counters: Add a service monitor to scrape the counters metrics
- 6bb058df - swh/staging: Active the counters metrics scraping
Toggle commit list-
d95098ea...4de61657 - 3 commits from branch
v316 deployed in staging
Ater some fight the migration was finally applied correctly:
swh@swh-toolbox-6bbd4df7d9-2kt95:~$ swh db --config-file=$SWH_CONFIG_FILENAME upgrade storage.proxies.masking --dbname swh-masking --module-config-key=masking_admin WARNING:swh.core.sentry:Sentry DSN not provided, events will not be sent. Usage: swh db upgrade [OPTIONS] MODULE Try 'swh db upgrade -h' for help. Error: Invalid value: Error: the given module (storage.proxies.masking) does not match the value stored in the database (storage). ---------------------------------- https://gitlab.softwareheritage.org/swh/devel/swh-storage/-/commit/26c3be97b25daae6b81554df8f0788cc7e9d0c35 swh-masking=# select * from dbmodule; dbmodule | single_row ----------+------------ storage | x (1 row) swh-masking=# update dbmodule set dbmodule='storage.proxies.masking'; UPDATE 1To fix for discrepancies in the configuration:
swh@swh-toolbox-6bbd4df7d9-2kt95:~$ diff -U3 /etc/swh/config-masking.yml config-masking.yml --- /etc/swh/config-masking.yml 2024-06-04 12:57:47.927615633 +0000 +++ config-masking.yml 2024-06-04 13:46:34.990300349 +0000 @@ -3,5 +3,6 @@ db: host=db1.internal.staging.swh.network port=5432 user=swh-masking dbname=swh-masking password=XXX masking_admin: - masking_db: host=db1.internal.staging.swh.network port=5432 user=swh-masking dbname=swh-masking + cls: postgresql + db: host=db1.internal.staging.swh.network port=5432 user=swh-masking dbname=swh-masking password=XXXswh@swh-toolbox-6bbd4df7d9-2kt95:~$ swh db --config-file=$SWH_CONFIG_FILENAME upgrade storage.proxies.masking --module-config-key=masking_admin WARNING:swh.core.sentry:Sentry DSN not provided, events will not be sent. INFO:swh.core.db.db_utils:Executing migration script '/opt/swh/.local/lib/python3.10/site-packages/swh/storage/proxies/masking/sql/upgrades/193.sql' WARNING:swh.core.db.db_utils:Asked for flavor only_masking, but module does not support database flavors INFO:swh.core.db.db_utils:Executing migration script '/opt/swh/.local/lib/python3.10/site-packages/swh/storage/proxies/masking/sql/upgrades/194.sql' WARNING:swh.core.db.db_utils:Asked for flavor only_masking, but module does not support database flavors Migration to version 194 doneWARNING:swh.core.db.db_utils:Asked for flavor only_masking, but module does not support database flavorsI suppose the message is due to some remaining data in the database
Please register or sign in to reply