Follow-up on this. Seems I had a minor bug in the deployed code which was causing the credentials bug to still occur. I tracked it down and fixed it in change Iea6b565c. Once deployed in production my credentials suddenly reappeared, which indicates this should indeed solve the problem (hopefully permanently).
- Ryan On Wed, Nov 21, 2012 at 1:25 PM, Ryan Lane <[email protected]> wrote: > I've pushed in a few patches that should kill off the no credentials bug > for all cases except first login for a new account. You may get that error > message one last time, but you shouldn't get it again otherwise. If you see > this error, please let me know. > > The bug was reintroduced when we switched to keystone and was triggered by > sessions (and openstack tokens) disappearing from memcache, like in cases > where memcache was restarted. If you had a long-lived token, then you would > receive a new session upon next visit to labsconsole but your openstack > tokens would be gone. I've added some tables to the database that'll save > your ldap domain and your openstack generic token, if you are using a > long-lived token. If your generic token is missing from memcache it'll pull > it from the database. > > The bug is still triggered when a new login occurs because authentication > isn't actually triggered on password reset. I'll add a fix for this soon. > > - Ryan >
_______________________________________________ Labs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/labs-l
