405 method not allowed

[Spencer Seidel]

After upgrading deb installation of MAAS to 2.5.0 beta 3, I was able to use the MAAS for a few screens but then got a 405 Method Not Allowed error on every attempt to access MAAS UI. If I close the window and try connecting again it seems to work.

I am running MAAS 2.5.0 beta 3 in a container installed via ppa:maas/next. I have also seen this error when running very recent versions of MAAS off the master branch.

See attached tarball for logs. Here is the output of the dpkg listing:

root@bionic-maas-run:~# dpkg -l '*maas*' | cat
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-===============================-============================================-============-=================================================
ii maas 2.5.0~beta3-7325-g1425f6d4c-0ubuntu1~18.04.1 all "Metal as a Service" is a physical cloud and IPAM
ii maas-cli 2.5.0~beta3-7325-g1425f6d4c-0ubuntu1~18.04.1 all MAAS client and command-line interface
un maas-cluster-controller <none> <none> (no description available)
ii maas-common 2.5.0~beta3-7325-g1425f6d4c-0ubuntu1~18.04.1 all MAAS server common files
ii maas-dhcp 2.5.0~beta3-7325-g1425f6d4c-0ubuntu1~18.04.1 all MAAS DHCP server
un maas-dns <none> <none> (no description available)
ii maas-proxy 2.5.0~beta3-7325-g1425f6d4c-0ubuntu1~18.04.1 all MAAS Caching Proxy
ii maas-rack-controller 2.5.0~beta3-7325-g1425f6d4c-0ubuntu1~18.04.1 all Rack Controller for MAAS
ii maas-region-api 2.5.0~beta3-7325-g1425f6d4c-0ubuntu1~18.04.1 all Region controller API service for MAAS
ii maas-region-controller 2.5.0~beta3-7325-g1425f6d4c-0ubuntu1~18.04.1 all Region Controller for MAAS
un maas-region-controller-min <none> <none> (no description available)
un python-django-maas <none> <none> (no description available)
un python-maas-client <none> <none> (no description available)
un python-maas-provisioningserver <none> <none> (no description available)
ii python3-django-maas 2.5.0~beta3-7325-g1425f6d4c-0ubuntu1~18.04.1 all MAAS server Django web framework (Python 3)
ii python3-maas-client 2.5.0~beta3-7325-g1425f6d4c-0ubuntu1~18.04.1 all MAAS python API client (Python 3)
ii python3-maas-provisioningserver 2.5.0~beta3-7325-g1425f6d4c-0ubuntu1~18.04.1 all MAAS server provisioning libraries (Python 3)
root@bionic-maas-run:~#

[Andres Rodriguez (andreserl)]

2018-10-16 11:02:52 twisted.scripts: [info] twistd 17.9.0 (/usr/bin/python3 3.6.6) starting up.
2018-10-16 11:02:52 twisted.scripts: [info] reactor class: twisted.internet.asyncioreactor.AsyncioSelectorReactor.
2018-10-16 11:02:54 stderr: [error] --- Logging error ---
2018-10-16 11:02:54 stderr: [error] Traceback (most recent call last):
2018-10-16 11:02:54 stderr: [error] File "/usr/lib/python3/dist-packages/twisted/internet/defer.py", line 1386, in _inlineCallbacks
2018-10-16 11:02:54 stderr: [error] result = g.send(result)
2018-10-16 11:02:54 stderr: [error] StopIteration: (3, '● maas-syslog.service - MAAS Syslog Service\n Loaded: loaded (/lib/systemd/system/maas-syslog.service; enabled; vendor preset: enabled)\n Active: inactive (dead) since Tue 2018-10-16 11:01:15 EDT; 1min 38s ago\n Docs: man:rsyslogd(8)\n http://docs.maas.io/\n Main PID: 636 (code=exited, status=0/SUCCESS)\n\nOct 16 11:00:39 bionic-maas-run systemd[1]: maas-syslog.service: Failed to reset devices.list: Operation not permitted\nOct 16 11:00:51 bionic-maas-run systemd[1]: maas-syslog.service: Failed to reset devices.list: Operation not permitted\nOct 16 11:00:53 bionic-maas-run systemd[1]: maas-syslog.service: Failed to reset devices.list: Operation not permitted\nOct 16 11:00:55 bionic-maas-run systemd[1]: maas-syslog.service: Failed to reset devices.list: Operation not permitted\nOct 16 11:00:55 bionic-maas-run systemd[1]: maas-syslog.service: Failed to reset devices.list: Operation not permitted\nOct 16 11:01:14 bionic-maas-run systemd[1]: maas-syslog.service: Failed to reset devices.list: Operation not permitted\nOct 16 11:01:15 bionic-maas-run systemd[1]: maas-syslog.service: Failed to reset devices.list: Operation not permitted\nOct 16 11:01:15 bionic-maas-run systemd[1]: Stopping MAAS Syslog Service...\nOct 16 11:01:15 bionic-maas-run rsyslogd[636]: [origin software="rsyslogd" swVersion="8.32.0" x-pid="636" x-info="http://www.rsyslog.com"] exiting on signal 15.\nOct 16 11:01:15 bionic-maas-run systemd[1]: Stopped MAAS Syslog Service.\n', '')
2018-10-16 11:02:54 stderr: [error]
2018-10-16 11:02:54 stderr: [error] During handling of the above exception, another exception occurred:
2018-10-16 11:02:54 stderr: [error]
2018-10-16 11:02:54 stderr: [error] Traceback (most recent call last):
2018-10-16 11:02:54 stderr: [error] File "/usr/lib/python3/dist-packages/twisted/internet/defer.py", line 1386, in _inlineCallbacks
2018-10-16 11:02:54 stderr: [error] result = g.send(result)
2018-10-16 11:02:54 stderr: [error] File "/usr/lib/python3/dist-packages/provisioningserver/utils/service_monitor.py", line 560, in _loadSystemDServiceState
2018-10-16 11:02:54 stderr: [error] returnValue((active_state_enum, process_state))
2018-10-16 11:02:54 stderr: [error] File "/usr/lib/python3/dist-packages/twisted/internet/defer.py", line 1363, in returnValue
2018-10-16 11:02:54 stderr: [error] raise _DefGen_Return(val)
2018-10-16 11:02:54 stderr: [error] twisted.internet.defer._DefGen_Return: (<SERVICE_STATE.OFF: 'off'>, 'dead')
2018-10-16 11:02:54 stderr: [error]
2018-10-16 11:02:54 stderr: [error] During handling of the above exception, anoth...

[Andres Rodriguez (andreserl)]

What it would seem to me is that MAAS was starting up. Recent changes in the startup process don't seem to hanbdle these thigns correctly though.

[Adam Collard (adam-collard)]

This bug has not seen any activity in the last 6 months, so it is being automatically closed.

If you are still experiencing this issue, please feel free to re-open.

MAAS Team