Closed
Bug 1065768
Opened 10 years ago
Closed 10 years ago
Please deploy server-syncstorage 1.5.10 to stage
Categories
(Cloud Services :: Operations: Deployment Requests - DEPRECATED, task)
Cloud Services
Operations: Deployment Requests - DEPRECATED
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: rfkelly, Assigned: bobm)
References
Details
(Whiteboard: [qa+])
This version of syncstorage changes the way ConflictErrors are reported for POST requests: Bug 1065750 - Don't report ConflictError as a 503 on POST requests This will hopefully reduce the level of background 503s to approximately what they were before the 1.5.9 deployment, and reduce the number of spurious "server maintenance" errors seen in the wild. Let's deploy this to stage, and through to production, with some urgency. Trivial change so I'm not too worried about loadtesting etc, just some basic sanity-checks should suffice.
Comment 1•10 years ago
|
||
OK, let's do this.
Assignee: nobody → bobm
Status: NEW → ASSIGNED
QA Contact: jbonacci
Assignee | ||
Comment 2•10 years ago
|
||
This has been deployed to stage.
Comment 3•10 years ago
|
||
Verified the following code on Sync1 - Sync4: server-syncstorage 1.5.10-1.el6 x86_64 41943288 Quick tests (remote integration) were successful. Starting 30min load on Sync1 and Sync4.
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Comment 4•10 years ago
|
||
To save time and maximize effort, going with a 45min combined... ;-)
Comment 5•10 years ago
|
||
45minute combined test is here: https://loads.services.mozilla.com/run/fbda6e22-9613-472a-af80-578a4c0bf5c2 Everything looks good from the dashboard. Checking logs...
You need to log in
before you can comment on or make changes to this bug.
Description
•