1631788 - Please migrate a single sync node in production on Monday May 4th at 11am EST

Status: RESOLVED INVALID

(Cloud Services Graveyard :: Operations: Sync, task, P2)

Description

[Rachel Tublitz [:rachel]]

We're ready to start the migration, assuming our testing in 1631787 doesn't yield anything critical.

Comment 1

[Rachel Tublitz [:rachel]]

Erik; can you confirm that this date works for your team?

Comment 2

[Erik Olson]

Bob is putting together a doc that has go/no go requirements from an ops perspective, assuming they are all met, that date should work.

Comment 3

[Bob Micheletto [:bobm]]

(In reply to Erik Olson from comment #2)

Bob is putting together a doc that has go/no go requirements from an ops perspective, assuming they are all met, that date should work.

Instead of a Go/No Requirements doc, I'm going to just make a few notes here:

Requirements:

• Dependent bugs are all closed and verified:
  • Bug 1630659 - HMAC issue
  • Bug 1630679 - Re-upload issue.
  • Bug 1631787 - Final round of client testing.
• Someone from the client development team reviews the testing procedures for Bug 1631787 to validate they are sound.
• Someone from the client development team reviews the results of the testing for Bug 1631787 to validate they have passed.

Comment 4

[Rachel Tublitz [:rachel]]

(In reply to Bob Micheletto [:bobm] from comment #3)

• Someone from the client development team reviews the testing procedures for Bug 1631787 to validate they are sound.

Lina is going to take a look here by Monday. Thanks in advance, Lina! When you're done, if you could verify here (or let us know if you have any issues/concerns) that would be great.

Comment 5

[Lina Butler [:lina]]

Thanks so much, Rachel! I reviewed the durable sync test plans in TestRail, and they look really good to me! Some notes:

• Larger quantities of data also increase the opportunity for running into other edge cases, like syncing during migration, so it's nice to have both!
• I noticed we have "user disconnects during migration", but not "user signs in to a new device during migration" (maybe when only some of their data has been migrated, or if the new device has data of its own). I guess these scenarios are two sides of the same coin, but I wonder if it's worth calling out explicitly?
• Some collections, like bookmarks, have a "validation" tab in about:sync. In addition to checking success logs (to make sure that, say, the client didn't reupload all data during the first sync after migration), it would be great to double-check that, and verify that there are no validation errors reported—or, if there are, they're the same pre-migration and post-migration.

Comment 6

[Rachel Tublitz [:rachel]]

Going to close this out for now as invalid since we just hit a few issues (here and here). Once we're confident we're ready to go, I'll re-open this with a new target date to get this started.