Created attachment 608551 [details]
happens/expected screenshot comparison
1. luci installed+started, user logged into it + keeping it opened
in the web browser (within active session timeframe)
2. install another version (perhaps even plain reinstall will do)
3. start the newly installed version (if not automatically)
4. try to continue in the previously opened session in the web browser
Login form with some links normally available only when logged in
(Homebase, Manage Clusters). Both links, when clicked, only
lead back to login form as the linked content requires authorization.
Login form as usual (i.e., no additional links).
See attached happens/expected screenshots comparison.
The other part of ungraceful handling of package update while
trying to work with luci continuously is a backtrace in luci.log.
This (probably) arises from the fact the old SSL connection is no longer
in use, something what the web browser (specifically, Firefox) does
not like either (new round of allowing certificate exception):
Exception happened during processing of request from
Traceback (most recent call last):
File "/usr/lib/python2.6/site-packages/paste/httpserver.py", line 1068,
File "/usr/lib64/python2.6/SocketServer.py", line 322,
self.RequestHandlerClass(request, client_address, self)
File "/usr/lib64/python2.6/SocketServer.py", line 617,
File "/usr/lib/python2.6/site-packages/paste/httpserver.py", line 442,
File "/usr/lib64/python2.6/BaseHTTPServer.py", line 329,
File "/usr/lib/python2.6/site-packages/paste/httpserver.py", line 431,
self.raw_requestline = self.rfile.readline()
File "/usr/lib64/python2.6/socket.py", line 450,
data = self._sock.recv(self._rbufsize)
Error: [('SSL routines', 'SSL3_READ_BYTES', 'sslv3 alert bad certificate')]
Tried hard, but cannot reproduce this bug anymore.
Huh, just managed to reproduce this, with reproducer as simple as:
1. stay at login page, perhaps came_from backlink to homebase is needed
2. restart luci
3. hit reload in the web browser
There was a bad instantiation of ClusterController.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.