I am testing upgrading an existing Wazo installation from 18.0. to 19.13 using this guide. I’ve run into some headaches that I thought I’d ask about here:
-
After running
wazo-upgradeand installing thewazo-uipackage some admin users from before the upgrade are not are able to log in. I am able to usewazo-auth-cli user listto view a list of users, but I don’t see any of the old admin accounts. I am able to login with my old account that is not listed. My current account is in theauth_usertable and I have thewazo_default_admin_policypolicy on my account, but another account that worked pre-upgrade does not have that policy. Is there a place in the newer interface to manage admin accounts? -
After running
wazo-dist-upgradeand rebooting, I can no longer log in to the web interface. The end of the process printed/usr/bin/wazo-dist-upgrade-buster: line 201: wazo-check-conffiles: command not found. Trying to login to the web interface fails and logs the following into/var/log/wazo-ui.log:
2019-11-14 15:36:59,014 [1295] (ERROR) (wazo_ui.errors): Unexpected error:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/wazo_ui/plugins/authentication/form.py", line 43, in validate
response = auth_client.token.new(expiration=60 * 60 * 12)
File "/usr/lib/python3/dist-packages/wazo_auth_client/commands/token.py", line 28, in new
self.raise_from_response(r)
File "/usr/lib/python3/dist-packages/xivo_lib_rest_client/command.py", line 25, in raise_from_response
response.raise_for_status()
File "/usr/lib/python3/dist-packages/requests/models.py", line 940, in raise_for_status
raise HTTPError(http_error_msg, response=self)
requests.exceptions.HTTPError: 400 Client Error: BAD REQUEST for url: https://localhost:9497/0.1/token
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/flask/app.py", line 1813, in full_dispatch_request
rv = self.dispatch_request()
File "/usr/lib/python3/dist-packages/flask/app.py", line 1799, in dispatch_request
return self.view_functions[rule.endpoint](**req.view_args)
File "/usr/lib/python3/dist-packages/flask_classful.py", line 231, in proxy
response = view(**request.view_args)
File "/usr/lib/python3/dist-packages/flask_classful.py", line 202, in inner
return fn(*args, **kwargs)
File "/usr/lib/python3/dist-packages/wazo_ui/plugins/authentication/view.py", line 25, in post
return self._login()
File "/usr/lib/python3/dist-packages/wazo_ui/plugins/authentication/view.py", line 33, in _login
if form.validate_on_submit():
File "/usr/lib/python3/dist-packages/flask_wtf/form.py", line 101, in validate_on_submit
return self.is_submitted() and self.validate()
File "/usr/lib/python3/dist-packages/wazo_ui/plugins/authentication/form.py", line 54, in validate
raise ValidationError(l_('Error with Wazo authentication server: %(error)s', error=e.message))
AttributeError: 'HTTPError' object has no attribute 'message'
Trying to list users with the wazo-auth-cli user list command prints 400 Client Error: BAD REQUEST for url: https://localhost:9497/0.1/token, and trying to get a token with curl gives an internal server error:
HTTP/1.1 500 INTERNAL SERVER ERROR
Content-Type: application/json
Content-Length: 37
Access-Control-Allow-Origin: *
Date: Thu, 14 Nov 2019 22:40:20 GMT
Server: Cheroot/6.5.4
{"message": "Internal Server Error"}
Tailing the /var/log/wazo-auth.log file fills the page with 404 errors as well.
- Trying to check for updates after upgrading to Buster with
wazo-upgradefails, and I have to runwazo-dist -m pelican-stretchagain. Runningwazo-upgradethen prints thatxivo-upgrade is already the newest version (19.14~20190925.180051.ce3a5c8.deb9)..