Last modified: 2014-02-25 10:58:33 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T63710, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 61710 - Jenkins: Consistently getting 503 Varnish in response to succesful login
Jenkins: Consistently getting 503 Varnish in response to succesful login
Status: RESOLVED FIXED
Product: Wikimedia
Classification: Unclassified
Continuous integration (Other open bugs)
wmf-deployment
All All
: Unprioritized normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-02-20 23:08 UTC by Krinkle
Modified: 2014-02-25 10:58 UTC (History)
3 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Krinkle 2014-02-20 23:08:09 UTC
As of late, when logging in to Jenkins I get a 503 error from Varnish in return (the green wmerror page, much like our php/wmerror one).

https://integration.wikimedia.org/ci/login?from=%2Fci%2F

It only does that for a successful login though, with a wrong password it just shows the login form again with the relevant error message.
Comment 1 Krinkle 2014-02-20 23:08:32 UTC
When I manually go back with cache disabled it shows me being logged in though, so it did somehow get through.
Comment 2 Antoine "hashar" Musso (WMF) 2014-02-20 23:57:08 UTC
Might be related to bug 58279, aka http redirects to https being cached in varnish and cache not varying by protocol.

Patch is https://gerrit.wikimedia.org/r/#/c/114464/ , will be deployed on monday.
Comment 3 Antoine "hashar" Musso (WMF) 2014-02-20 23:57:52 UTC
Err patch is https://gerrit.wikimedia.org/r/#/c/113958/ , will be deployed on monday.
Comment 4 Antoine "hashar" Musso (WMF) 2014-02-25 10:58:33 UTC
The patch got deployed and the misc varnish cache is now instructed to vary by protocol (Vary: X-Forwarded-Proto).  I guess that would solve this bug as well.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links