Old sessionid cookie causes 500 Internal Server Error at login
Bug #1338836 reported by
Nathan Ward
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Dashboard (Horizon) |
Expired
|
Undecided
|
Unassigned |
Bug Description
After switching to a different cloud, Django's old "sessionid" cookie causes Horizon to greet you with the 500 Internal Server Error page. Clearing browser cookies or deleting just the "sessionid" cookie (e.g. in Chrome Dev Tools > Resources > Cookies) and refreshing is a workaround to bring the user back to a working login screen. Could this happen because request.
https:/
tags: | added: horizon-core |
tags: |
added: dashboard-core removed: horizon-core |
To post a comment you must log in.
I think this was a known issue when we switched from a date time object to an int for time (...or was it vice-versa?). The change was made forward-compatible but not backwards compatible, since except in the unlikely event of a rollback sometime after an upgrade it shouldn't happen. Could you clarify if/how you were encountering this situation in the real world? Thank you.