Closed Bug 792267 Opened 14 years ago Closed 14 years ago

deploy persona train-2012.08.17 to production

Categories

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

x86_64
Linux
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: lhilaiel, Assigned: gene)

Details

(Whiteboard: [qa+])

Version: 80480e1 (0.2012.08.17.1) RPM location: https://ozten.com/random/identity/browserid-server-2.2012.08.17-1.el6_109133.x86_64.rpm RPM md5: 376e75c36f7e519e20fd55f91adbe4ed
Assignee: nobody → gene
QA Contact: jrgm
6:13pm deployment at SCL2 completed, passing on to :jrgm for testing
:jrgm gives a thumbs up to the site in SCL2 6:25pm I've re-enabled SCL2 and drained PHX1
Things are looking good so far. We're going to let it sit on the new code until 7:10pm and then move forward if everything still looks good.
7:19pm started deploying to PHX1 25 minute delay due to weird puppet client behaviour where clients were not taking the current config on the puppetmaster short delay due to bidpush on adm1.phx1 not working (bad path to fping, missing zeus-api ruby modules etc) 8:02pm finished updating PHX1 and handed the environment to :jrgm for testing
And for records sake, we began at SCL2 when I drained traffic off of it at 5:52pm
:jrgm gave sign off for PHX1 and at 8:27pm I re-enabled it in dynect such that traffic is now flowing to both SCL2 and PHX1
Deployment complete
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.