If you are logged out of a session in Horizon and log back in, you get an error message that should have been on the login screen.

Bug #1021894 reported by John Postlethwait
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Dashboard (Horizon)
Won't Fix
Low
Unassigned

Bug Description

Repro:

1) Log in to Horizon.
2) Open your browser's cookies and delete the cookies for the Horizon dashboard you are on.
3) Refresh the page.

Expected:

You are placed on the login page with an error that says "Error: Please log in to continue." You may then log in using the login dialog and be redirected back to the page you were on before you deleted the cookies.

Actual:

You ARE placed on the login page, but no error is show. Upon successfully logging in, you receive a flash notification that says "Error: Please log in to continue." which is wrong because I DID just log in...

I believe this is due to the error queuing that was done for flash notifications so that you no longer receive messages on the login screen like "Error: Unable to retrieve keypair list." when you are logged out, which made no sense and were contextually irrelevant on the login page.

Revision history for this message
John Postlethwait (john-postlethwait) wrote :
Revision history for this message
Gabriel Hurley (gabriel-hurley) wrote :

In working on the auth refactor review that's up right now I noticed that there's some messages that are no longer being displayed in the right place as well. Thanks for filing the bug.

Changed in horizon:
assignee: nobody → Gabriel Hurley (gabriel-hurley)
importance: Undecided → Medium
milestone: none → folsom-3
status: New → Confirmed
Revision history for this message
Jake Dahn (jakedahn) wrote :

I think the state of this bug has changed since it was filed.

The current behavior is that I do not receive an error at all once I'm logged back in. Perhaps gabriel's auth refactor changed some of this.

That said the expected behavior is to see an error on the login page when your session expires, correct?

Revision history for this message
Gabriel Hurley (gabriel-hurley) wrote :

I believe you are correct. The inappropriate errors are no longer shown after logging back in, but you may not know why you were logged out. I'm okay with bumping that to a wishlist feature, though.

The complexity involved in passing along only *specific* messages to the login page is non-trivial in any way I've been able to come up with.

Changed in horizon:
importance: Medium → Wishlist
milestone: folsom-3 → none
assignee: Gabriel Hurley (gabriel-hurley) → Nebula (nebula)
Revision history for this message
Gabriel Hurley (gabriel-hurley) wrote :

John P. has convinced me to continue classifying this as bug, however I still have no thought of or heard any solution that isn't a hack, so I'm leaving it untargeted for now.

Changed in horizon:
importance: Wishlist → Low
assignee: Nebula (nebula) → nobody
Revision history for this message
Gabriel Hurley (gabriel-hurley) wrote :

I'm closing this one out since the original bug report *is* fixed. I've opened a new ticket for the issue discussed in the comments: https://bugs.launchpad.net/horizon/+bug/1060426

Changed in horizon:
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.