after default installation of maas the rack and region controller are not connected

Bug #1560971 reported by Dominic
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
maas (Ubuntu)
New
Undecided
Unassigned

Bug Description

1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu
Description: Ubuntu Xenial Xerus (development branch)
Release: 16.04

2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center
maas:
  Installiert: 2.0.0~alpha3+bzr4810-0ubuntu1
  Installationskandidat: 2.0.0~alpha3+bzr4810-0ubuntu1
  Versionstabelle:
 *** 2.0.0~alpha3+bzr4810-0ubuntu1 500
        500 http://de.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
        500 http://de.archive.ubuntu.com/ubuntu xenial/main i386 Packages
        100 /var/lib/dpkg/status

3) What you expected to happen
i expected that the rack and region will be connected after both get installed automatically

4) What happened instead
after default installation of maas the rack and region controller are not connected
i had to reconfig rack controller with
  sudo dpkg-reconfigure maas-rack-controller
(from https://maas.ubuntu.com/docs/rack-configuration.html)
and edit the default url 'localhost:5240' to my interface ip address

Revision history for this message
Spyderdyne (spyderdyne) wrote :

Same issue on Ubuntu Mate 16.04 ARMHF (Raspberry Pi 3B):

VERSIONS
root@juju-rack2:~# cat /etc/issue
Ubuntu 16.04.1 LTS \n \l

root@juju-rack2:~# uname -a
Linux juju-rack2.home.spyderdyne.net 4.4.43-v7+ #948 SMP Sun Jan 15 22:20:07 GMT 2017 armv7l armv7l armv7l GNU/Linux

MAAS Version 2.1.3+bzr5573-0ubuntu1 (16.04.1) - From PPA stable...

Unfortunately, dpkg-reconfigure doesn't fix the issue. I manually added the API key back to try to correct following the instructions here:

https://maas.ubuntu.com/docs/rack-configuration.html#registration

running "dpkg-reconfigure maas-rack-controller" per the instructions provided.

Still not connected. Checking the log at /var/log/maas/rackd.log I see it was unable to connect to itself at 127.0.0.1 and finally shut itself down:

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/twisted/internet/defer.py", line 588, in _runCallbacks
    current.result = callback(current.result, *args, **kw)
  File "/usr/lib/python3/dist-packages/twisted/internet/defer.py", line 1184, in gotResult
    _inlineCallbacks(r, g, deferred)
  File "/usr/lib/python3/dist-packages/twisted/internet/defer.py", line 1126, in _inlineCallbacks
    result = result.throwExceptionIntoGenerator(g)
  File "/usr/lib/python3/dist-packages/twisted/python/failure.py", line 389, in throwExceptionIntoGenerator
    return g.throw(self.type, self.value, self.tb)
--- <exception caught here> ---
  File "/usr/lib/python3/dist-packages/provisioningserver/rpc/clusterservice.py", line 978, in update
    info = yield self._fetch_rpc_info(info_url)
twisted.web.error.Error: 500 INTERNAL SERVER ERROR
2017-01-19 12:15:59 -: [info] Received SIGTERM, shutting down.
2017-01-19 12:17:20 -: [info] twistd 16.0.0 (/usr/bin/python3 3.5.2) starting up.
2017-01-19 12:17:20 -: [info] reactor class: twisted.internet.epollreactor.EPollReactor.

Rebooting show the config updated successfully, but the region controller is refusing the rack controller now:

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/twisted/internet/defer.py", line 588, in _runCallbacks
    current.result = callback(current.result, *args, **kw)
  File "/usr/lib/python3/dist-packages/twisted/internet/defer.py", line 1184, in gotResult
    _inlineCallbacks(r, g, deferred)
  File "/usr/lib/python3/dist-packages/twisted/internet/defer.py", line 1126, in _inlineCallbacks
    result = result.throwExceptionIntoGenerator(g)
  File "/usr/lib/python3/dist-packages/twisted/python/failure.py", line 389, in throwExceptionIntoGenerator
    return g.throw(self.type, self.value, self.tb)
--- <exception caught here> ---
  File "/usr/lib/python3/dist-packages/provisioningserver/rpc/clusterservice.py", line 978, in update
    info = yield self._fetch_rpc_info(info_url)
twisted.web.error.Error: 500 INTERNAL SERVER ERROR
2017-01-19 12:15:59 -: [info] Received SIGTERM, shutting down.
2017-01-19 12:17:20 -: [info] twistd 16.0.0 (/usr/bin/python3 3.5.2) starting up.
2017-01-19 12:17:20 -: [info] reactor class: twisted.internet.epollreactor.EPollReactor.

Still digging...

Revision history for this message
Spyderdyne (spyderdyne) wrote :
Download full text (13.2 KiB)

RPC connection failed:

    info = yield self._fetch_rpc_info(info_url)
twisted.web.error.Error: 500 INTERNAL SERVER ERROR
2017-01-19 12:15:59 -: [info] Received SIGTERM, shutting down.
2017-01-19 12:17:20 -: [info] twistd 16.0.0 (/usr/bin/python3 3.5.2) starting up.
2017-01-19 12:17:20 -: [info] reactor class: twisted.internet.epollreactor.EPollReactor.
2017-01-19 12:40:55 -: [info] Received SIGTERM, shutting down.
2017-01-19 12:42:27 -: [info] twistd 16.0.0 (/usr/bin/python3 3.5.2) starting up.
2017-01-19 12:42:27 -: [info] reactor class: twisted.internet.epollreactor.EPollReactor.
2017-01-19 12:42:28 provisioningserver.rpc.clusterservice: [info] Region not available: Connection was refused by other side: 111: Connection refused. (While requesting RPC info at b'http://[::ffff:192.168.199.2]:5240/MAAS/rpc/').
2017-01-19 12:42:29 provisioningserver.rpc.clusterservice: [info] Region not available: Connection was refused by other side: 111: Connection refused. (While requesting RPC info at b'http://[::ffff:192.168.199.2]:5240/MAAS/rpc/').

Port is alive:

root@juju-rack2:~# netstat -untap | grep 5240
tcp6 0 0 :::5240 :::* LISTEN 1235/python3
tcp6 0 0 :::5240 :::* LISTEN 1217/python3
tcp6 0 0 :::5240 :::* LISTEN 1203/python3
tcp6 0 0 :::5240 :::* LISTEN 1211/python3
tcp6 0 0 192.168.199.2:5240 192.168.199.2:39136 TIME_WAIT -
tcp6 0 0 192.168.199.2:5240 192.168.199.2:39184 TIME_WAIT -
tcp6 0 0 192.168.199.2:5240 192.168.199.2:39172 TIME_WAIT -
tcp6 0 0 192.168.199.2:5240 192.168.199.2:39308 TIME_WAIT -
tcp6 0 0 192.168.199.2:5240 192.168.199.2:39234 TIME_WAIT -
tcp6 0 0 192.168.199.2:5240 192.168.199.2:39246 TIME_WAIT -
tcp6 0 0 192.168.199.2:5240 192.168.199.2:39010 TIME_WAIT -
tcp6 0 0 192.168.199.2:5240 192.168.199.2:39096 TIME_WAIT -
tcp6 0 0 192.168.199.2:5240 192.168.199.2:39210 TIME_WAIT -
tcp6 0 0 192.168.199.2:5240 192.168.199.2:39222 TIME_WAIT -
tcp6 0 0 192.168.199.2:5240 192.168.199.2:38986 TIME_WAIT -
tcp6 0 0 192.168.199.2:5240 192.168.199.2:39148 TIME_WAIT -
tcp6 0 0 192.168.199.2:5240 192.168.199.2:39060 TIME_WAIT -
tcp6 0 0 192.168.199.2:5240 192.168.199.100:53545 ESTABLISHED 1211/python3
tcp6 0 0 192.168.199.2:5240 192.168.199.2:39022 TIME_WAIT -
...

MaaS RPC service appears to be down according to /var/log/maas/maas.log:

Jan 19 11:54:32 juju-rack2 maas.bootsources: [info] Updated boot sources cache.
Jan 19 11:54:32 juju-rack2 maas.bootresources: [info] Started importing of boot im...

Revision history for this message
Spyderdyne (spyderdyne) wrote :

Apparently there was something in my process that caused it to break. After wiping to a clean state, purging everything (sudo dpkg --remove --force-remove-reinstreq maas), and installing again there were no issues.

Disregard my comments, nothing to see here.

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.