Closed Bug 887904 Opened 12 years ago Closed 12 years ago

CSRF failures on MozTrap dev and staging - unable to log in

Categories

(Mozilla QA Graveyard :: MozTrap, defect)

defect
Not set
major

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: stephend, Assigned: cturra)

References

()

Details

(Whiteboard: [fromAutomation])

STR: 1. Load https://moztrap.allizom.org/results/runs/ 2. Click Sign In 3. Sign in Actual Results: Forbidden (403) CSRF verification failed. Request aborted. FWIW, this started last night: http://qa-selenium.mv.mozilla.com:8080/view/MozTrap/job/moztrap.staging/ Sometime between: Failed > Console Output #805 Jun 26, 2013 7:47:11 PM 2MB Success > Console Output #804 Jun 26, 2013 2:59:53 PM 150KB
Note that this is also affecting Affiliates-stage [1], which started failing with this error sometime between 5:04pm and 8:44pm on June 26th. [1] http://affiliates.allizom.org
-> cturra, to work the same magic as in bug 888013!
Assignee: nobody → cturra
looks like we missed back porting this memcache name change into stage and dev for moztrap. this /should/ now be resolved o/
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Verified FIXED: 15:16 qatestbot: Yippie, build fixed! 15:16 qatestbot: Project moztrap.dev.saucelabs build #597:FIXED in 7 min 38 sec: http://qa-selenium.mv.mozilla.com:8080/job/moztrap.dev.saucelabs/597/ 15:16 qatestbot: Yippie, build fixed! 15:16 qatestbot: Project moztrap.stage.saucelabs build #600:FIXED in 8 min 1 sec: http://qa-selenium.mv.mozilla.com:8080/job/moztrap.stage.saucelabs/600/ Thanks again!
Status: RESOLVED → VERIFIED
Product: Mozilla QA → Mozilla QA Graveyard
You need to log in before you can comment on or make changes to this bug.