Closed Bug 873336 Opened 12 years ago Closed 11 years ago

Please deploy persona train-2013.05.08.4 to staging environment

Categories

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

x86
Linux
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: jrgm, Assigned: jrgm)

Details

This brings in fixes for: > * verifier parameters for forceIssuer and allowUnverified now have an experimental_ prefix > * Fix for users who are unable to sign out: issue #3386, #3398 > * confirm email link page is all white with no error on screen: issue #3362, #3397 > * [main site] error/wait/delay screen has transparent background: issue #3393, #3396 * new SHA: fe8c9d687007bcebb85b75bbc28b22baa955b2a1 * branch: train-2013.05.08 * repo: https://github.com/mozilla/browserid/tree/train-2013.05.08 I will build that rpm and deploy to physical stage now and check it out there. And then look at pushing this onto aws stage.
> build command: ./build.sh browserid train-2013.05.08 fe8c9d687007bcebb85b75bbc28b22baa955b2a1 > output rpm on r6: /home/jrgm/workspace/browserid/rpmbuild/RPMS/x86_64/browserid-server-0.2013.05.08-4.el6_116107.x86_64.rpm
I wsa setting up to update the rpm manually in stage and made a mistake, which was that I left on webhead running the updated code, which led to edwong noting problems with receiving content that was mismatched, leading to non-cache-poisoning 404 for entrained js files (which is good). https://github.com/mozilla/browserid/issues/3439 But at the same time, it was noted that myfavoritebeer.org was failing to call diresworb.org/verify via the proxy for that domain name - https://github.com/mozilla/browserid/issues/3437 It got a little confusing to locate the actual proxy, but in the end it appears to just that the apache proxy is not re-resolving DNS names - https://github.com/mozilla/browserid/issues/3440, and restarting the proxy solved things for now. I may try another update with this update (not tonight) where I `svc -d /service/browerid-*` on a few stage servers, rpm -U with the new rpm on those servers, then down the other set of running servers, and up the updated servers (doing the ~equivalent of how we release in production). Or maybe I won't and not do this on the weekend.
Resolving all stage-deploy bugs older than 60 days.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.