Closed Bug 1203391 Opened 10 years ago Closed 10 years ago

Please deploy shavar 0.6.5.1 to STAGE

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:
RESOLVED WONTFIX

People

(Reporter: cloud-services-qa, Assigned: ckolos)

Details

this has already been deployed to STAGE. load and e2e-testing is underway - test results will be posted in this deployment ticket.
Assignee: nobody → ckolos
Status: NEW → RESOLVED
Closed: 10 years ago
QA Contact: rpappalardo
Resolution: --- → FIXED
stack snapshot from :ckolos shavar-stage-83 ​ Shavar stack running 0.6.5.1 code​ c4.2xl instances TCP/Socket optimizations applied heka logging enabled 3 ELB's. shavar-load-3elb.stage.mozaws.net shavar-stage-79 ​​ Shavar stack running 0.6.5.1 code​ c4.2xl instances shavar-load-test.stage.mozaws.net shavar-stage-76 ​ Shavar stack running 0.6.5.1 code m3.medium instances ckshavar.stage.mozaws.net shavar-stage-74 ​ Shavar stack running 0.6.5.1 code​ m3.medium instances​ shavar.stage.mozaws.net
Moving on to 0.6.5.2 Bug 1204668 to include fix for missing data freshness check. Production deployment has been re-scheduled for Wed. @1:30PST to allow time to complete load & e2e testing see: Bug 1204668 - Please deploy shavar 0.6.5.2 to STAGE
Resolution: FIXED → WONTFIX
You need to log in before you can comment on or make changes to this bug.