Closed
Bug 1286535
Opened 8 years ago
Closed 8 years ago
Please deploy kinto-dist 0.6.1 release to kinto-settings STAGE
Categories
(Cloud Services :: Operations: Deployment Requests - DEPRECATED, task)
Cloud Services
Operations: Deployment Requests - DEPRECATED
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: rhubscher, Assigned: dmaher)
References
Details
Reporter | ||
Updated•8 years ago
|
Blocks: kinto-dist-0.6.3-prod
Reporter | ||
Comment 1•8 years ago
|
||
A migration needs to be run. kinto --ini kinto.ini migrate
Assignee | ||
Comment 2•8 years ago
|
||
(In reply to Rémy Hubscher (:natim) from comment #1) > A migration needs to be run. > > kinto --ini kinto.ini migrate [dmaher@ip-172-31-54-164 kinto-dist]$ ./bin/kinto --ini config/kinto.ini migrate event='Backend settings referring to cliquet are DEPRECATED. Please update your kinto.cache_backend setting to kinto.core.cache.postgresql (was: cliquet.cache.postgresql).' event='Backend settings referring to cliquet are DEPRECATED. Please update your kinto.logging_renderer setting to kinto.core.logs.MozillaHekaRenderer (was: cliquet.logs.MozillaHekaRenderer).' event='Backend settings referring to cliquet are DEPRECATED. Please update your kinto.permission_backend setting to kinto.core.permission.postgresql (was: cliquet.permission.postgresql).' event='Backend settings referring to cliquet are DEPRECATED. Please update your kinto.storage_backend setting to kinto.core.storage.postgresql (was: cliquet.storage.postgresql).' /data/kinto-dist/lib/python2.7/site-packages/kinto/core/storage/postgresql/client.py:87: UserWarning: Reuse existing PostgreSQL connection. Parameters permission_* will be ignored. warnings.warn(msg) /data/kinto-dist/lib/python2.7/site-packages/kinto/core/storage/postgresql/client.py:87: UserWarning: Reuse existing PostgreSQL connection. Parameters cache_* will be ignored. warnings.warn(msg) [dmaher@ip-172-31-54-164 kinto-dist]$
Assignee | ||
Updated•8 years ago
|
Flags: needinfo?(rhubscher)
Assignee | ||
Comment 3•8 years ago
|
||
07:27:55 < natim> The warnings are correct yes 07:58:12 < phrawzty> natim: ok. should we worry about those errors? 07:58:32 < natim> phrawzty: no I don't think so 07:58:37 < phrawzty> chartjes: ran natim's migration, and the next xml2kinto run exited 0 07:58:44 < phrawzty> chartjes: - 1 records to create. 07:58:44 < phrawzty> - 1 records to delete. 07:58:44 < phrawzty> - 0 records to update. 07:58:50 < natim> Ok so it worked :)
Flags: needinfo?(rhubscher) → needinfo?(chartjes)
Comment 4•8 years ago
|
||
TESTING ======= * verified that 'QA cert' in staging contained expected values by looking at https://kinto.stage.mozaws.net/v1/buckets/blocklists/collections/certificates/records * updated 'QA cert' using https://addons.allizom.org/en-US/admin/models/blocklist/blocklistissuercert/ and changed the issuer and serial number * requested that :phrawzty activate the xml2kinto job to move the blocklist details into Kinto * verified that 'QA cert' in staging contained newly updated values by https://kinto.stage.mozaws.net/v1/buckets/staging/collections/certificates/records * verified that 'QA cert' is also correctly updated at https://kinto.stage.mozaws.net/v1/buckets/blocklists/collections/certificates/records * no indication that the updated certificates have not been correctly signed. No certificates with the status of waiting to be signed. QA approves 0.6.1 deploy to staging
Flags: needinfo?(chartjes)
Reporter | ||
Updated•8 years ago
|
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Reporter | ||
Updated•8 years ago
|
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•