Last modified: 2013-04-24 18:33:30 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 T41792, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 39792 - Labsconsole session is omnipresent
Labsconsole session is omnipresent
Status: RESOLVED FIXED
Product: Wikimedia Labs
Classification: Unclassified
General (Other open bugs)
unspecified
All All
: Low normal
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-08-30 08:52 UTC by Damian Z
Modified: 2013-04-24 18:33 UTC (History)
3 users (show)

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


Attachments

Description Damian Z 2012-08-30 08:52:08 UTC
Since the upgrade labs console has been dropping my session more often, or so I thought. It turns out it thinks I'm logged out and logged in at the same time.

For example;
Hit https://labsconsole.wikimedia.org/wiki/Special:NovaInstance = Login required
Hit https://labsconsole.wikimedia.org/wiki/Main_Page = Logged in

Hit https://labsconsole.wikimedia.org/wiki/Special:NovaInstance = Login required
Hit https://labsconsole.wikimedia.org/wiki/Main_Page = Logged in

Is there a timing issue with keystone expiring before mediawiki, is it possible to increase the timeout? Having to login multiple times a day quickly gets annoying.
Comment 1 Damian Z 2012-10-13 16:58:34 UTC
Related to this - can we not store the session in the db? Currently it's in memcached which if restarted for any reason causes a 'no nova credentials' error message.

That error in its self for our use case is silly, as nova is backed by ldap being able to login to labsconsole in the first place implies you have a nova login and as the check is after the 'am I logged in' check it's redundant.

Changing it to force a logout breaks others use cases but having the token stored properly in the db, like the mediawiki session token would fix this.
Comment 2 Ryan Lane 2013-04-24 18:33:30 UTC
I haven't seen this issue in quite a long time. I believe it's fixed.

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


Navigation
Links