Closed Bug 1105529 Opened 11 years ago Closed 11 years ago

Please deploy server-syncstorage 1.5.11 to production

Categories

(Cloud Services :: Operations: Deployment Requests - DEPRECATED, task)

Product:
Cloud Services
Component:
Operations: Deployment Requests - DEPRECATED
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: kthiessen, Unassigned)

References

Details

(Whiteboard: [qa-automation-blocked][qa+])

+++ This bug was initially created as a clone of Bug #1094587 +++ This version of syncstorage tweaks some logging and adds a potential workaround for an apparent TokuDB bug: Bug 1063284 - Log at higher level when killing interrupted sql commands Bug 1057892 Comment 32 - workaround for TokuDB errors on PUT /meta/global This will hopefully reduce the level of 503s due to Bug 1057892 to close to zero.
Taking this ticket.
Status: NEW → ASSIGNED
Stage deployment complete.
(In reply to Bob Micheletto [:bobm] from comment #2) > Stage deployment complete. Correction: wrong ticket.
Bob, when can this finally be done? Thanks.
Flags: needinfo?(bobm)
Whiteboard: [qa+] → [qa-automation-blocked][qa+]
(In reply to Henrik Skupin (:whimboo) from comment #4) > Bob, when can this finally be done? Thanks. The latest two servers built in the production environment are running the 1.5.11 code base. The rest of the nodes will be upgraded shortly. However, it is important to here re-iterate that the primary purpose of the Sync 1.5 production environment is to support Fx users, and that Fx users were not adversely impacted by this bug.
Flags: needinfo?(bobm)
This has been deployed to production. Closing ticket.
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Deployment verified.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.