This isn't a huge problem but we should avoid failures when we can. I had an older installation and I force updated it. The old system still used krb as the login plugin name and it blew up trying to configure it:
DEBUG(ipsilon/util/errors.py:33 Errors.handler()): ['500 Internal Server Error', 'The server encountered an unexpected condition which prevented it from fulfilling the request.', 'Traceback (most recent call last):\n File "/usr/lib/python2.7/site-packages/cherrypy/_cprequest.py", line 656, in respond\n response.body self.oldhandler(args, kwargs)\n File "/usr/lib/python2.7/site-packages/cherrypy/_cpdispatch.py", line 34, in call\n return self.callable(*self.args, self.kwargs)\n File "/usr/lib/python2.7/site-packages/ipsilon/util/page.py", line 106, in call\n return op(args, **kwargs)\n File "/usr/lib/python2.7/site-packages/ipsilon/login/common.py", line 281, in root\n plugin plugins.available[first]\nKeyError: u\'krb\'\n', '3.2.2']
Fields changed
milestone: => 1.1
milestone: 1.1 => 1.2
owner: => rcritten rhbz: => status: new => accepted
https://pagure.io/ipsilon/pull-request/52
patch_available: 0 => 1
master: 9f806d7
resolution: => fixed status: accepted => closed
Metadata Update from @rcritten: - Issue assigned to rcritten - Issue set to the milestone: 1.2
Log in to comment on this ticket.