Closed Bug 1703107 Opened 4 years ago Closed 4 years ago

Please update Phabricator to 2021 Week 13

Categories

(Cloud Services :: Operations: Phabricator, task)

task
Not set
normal

Tracking

(conduit-pushaccept production)

RESOLVED FIXED
Tracking Status
conduit-push accept production

People

(Reporter: dkl, Assigned: bobm)

Details

Please update Phabricator to 2021 Week 13

https://secure.phabricator.com/w/changelog/2021.13/

{
  "moz_phabricator_commit": "dbdae99ebc2d9adc58e2d445dae52209d84a8b76",
  "moz_phabricator_version": "dbdae99ebc2d9adc58e2d445dae52209d84a8b76",
  "moz_phabricator_source": "https://github.com/mozilla-services/phabricator-extensions",
  "build": "https://circleci.com/gh/mozilla-services/phabricator-extensions/419"
}

Database migrations required: Yes

Migration Risk Duration Notes
20210315.affectedpath.01.epoch.sql 3,935 ms
20210315.affectedpath.02.repositoryid.sql 3,624 ms
20210316.almanac.01.device-mailkey.php 26 ms
20210316.almanac.02.device-dropmailkey.sql 50 ms
20210316.almanac.03.device-status.sql 30 ms
20210316.almanac.04.device-status-value.sql 1 ms
20210316.almanac.05.service-mailkey.php 3 ms
20210316.almanac.06.service-dropmailkey.sql 37 ms
20210316.almanac.07.binding-mailkey.php 5 ms
20210316.almanac.08.binding-dropmailkey.sql 33 ms
20210316.almanac.09.namespace-mailkey.php 8 ms
20210316.almanac.10.namespace-dropmailkey.sql 30 ms
20210316.almanac.11.network-mailkey.php 2 ms
20210316.almanac.12.network-dropmailkey.sql 27 ms
20210316.almanac.13.event-mailkey.php 841 ms
20210316.almanac.14.event-dropmailkey.sql 314 ms
20210316.almanac.15.intiative-mailkey.php 14 ms
20210316.almanac.16.initiative-dropmailkey.sql 38 ms

"Duration" is the duration for this install, and may not be representative.

This release has a large number of migrations, but almost all of them (those containing "almanac" in the name) are trivial and should take significantly less than a second to apply. See T13065.

The two "affectedpath" migrations affect a larger table and may take longer: a very rough estimate for both migrations combined is 6 minutes per million revisions.

Documentation regeneration: No

Deploy to phabricator-dev first for testing.

Ready for push to phab-dev for QA

Flags: needinfo?(bobm)

Dev deployment complete.

Flags: needinfo?(bobm) → needinfo?(dkl)

Development is good. Ready for push to stage.

Flags: needinfo?(dkl) → needinfo?(bobm)

master had a new patch added so making a new image for deployment.

Flags: needinfo?(bobm)

New image complete. Updated comment 0 with the latest JSON info. Please push to phab-dev for quick QA.

Flags: needinfo?(bobm)

Dev deployment round II complete.

Flags: needinfo?(bobm) → needinfo?(dkl)

Phab-dev is good again. Ready for stage.

Flags: needinfo?(dkl) → needinfo?(bobm)
Verifying database schemata on "mozphab-phabhost-rds-devsvcstage-201807261950.cwyrdopfjxck.us-west-2.rds.amazonaws.com:3306"...


Database                 Table                     Name         Issues
phabricator_differential differential_affectedpath repositoryID Surplus Key
phabricator_differential differential_affectedpath key_path     Missing Key

Found 2 adjustment(s) to apply, detailed above.

You can review adjustments in more detail from the web interface, in Config > Database Status. To better understand the adjustment workflow, see "Managing Storage Adjustments" in the documentation.

MySQL needs to copy table data to make some adjustments, so these migrations may take some time.


    Apply these schema adjustments? [y/N] y

Applying schema adjustments...
Done.
Completed applying all schema adjustments.
 ANALYZE  Analyzing tables...
Done.
 ANALYZED  Analyzed 540 table(s).

Stage deployment complete. Schema migration complete, less than a minute.

Flags: needinfo?(bobm) → needinfo?(dkl)

Stage is good. On to prod.

Flags: needinfo?(dkl) → needinfo?(bobm)
Database                 Table                     Name         Issues
phabricator_differential differential_affectedpath repositoryID Surplus Key
phabricator_differential differential_affectedpath key_path     Missing Key

Found 2 adjustment(s) to apply, detailed above.

You can review adjustments in more detail from the web interface, in Config > Database Status. To better understand the adjustment workflow, see "Managing Storage Adjustments" in the documentation.

MySQL needs to copy table data to make some adjustments, so these migrations may take some time.


    Apply these schema adjustments? [y/N] y

Applying schema adjustments...
Done.
Completed applying all schema adjustments.
 ANALYZE  Analyzing tables...
Done.
 ANALYZED  Analyzed 540 table(s).

Production deployment complete.

Flags: needinfo?(bobm) → needinfo?(dkl)

Thanks!

Status: ASSIGNED → RESOLVED
Closed: 4 years ago
Flags: needinfo?(dkl)
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.