MAAS will not import new images if it cannot connect to a cluster controller

Bug #1395120 reported by Mike Rushton
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
MAAS
Invalid
Critical
Unassigned

Bug Description

MAAS version 1.7.0+bzr3299-0ubuntu1~trusty

Related to bug: https://bugs.launchpad.net/maas/+bug/1394339

After failing to remove the cluster controller from the MAAS webUI, I ran the following to attempt to start over:

sudo apt-get remove --purge maas-cli maas-cluster-controller maas-common maas-dhcp maas-dns maas-region-controller maas-region-controller-min python-django-maas python-maas-client python-maas-provisioningserver curtin-common maas python-curtin python-psycopg2 python-txtftp postgres* ; sudo apt-get autoremove ; sudo apt-get clean

When given the choice I picked remove/purge/drop all configs and databases.

I also ran the following to continue the cleanup process:

sudo rm /etc/dbconfig-common/maas-region-controller.conf /var/tmp/maas* /usr/share/maas/ /etc/maas /var/lib/maas /var/log/upstart/maas* /var/lib/ucf/cache/*maas*

and rebooted.

Now starting from scratch, I should be able to install maas, configure, login, configure and start importing images.

The following traceback from /var/log/maas/maas-django.log shows the machine still trying to connect to 10.1.10.11 which is the 2nd cluster controller I had originally setup, connected, imported images to and in the end shut down and attempted to remove.

INFO 2014-11-21 14:03:14,942 twisted RegionServer connection established (HOST:IPv4Address(TCP, '10.245.128.2', 48181) PEER:IPv4Address(TCP, '10.1.10.11', 51630))
INFO 2014-11-21 14:03:14,946 twisted RegionServer connection established (HOST:IPv4Address(TCP, '10.245.128.2', 51702) PEER:IPv4Address(TCP, '10.1.10.11', 35831))
INFO 2014-11-21 14:03:14,960 twisted Cluster '3ff52dfe-454b-4a91-bef5-5cc3bb111460' FAILED authentication; dropping connection.
INFO 2014-11-21 14:03:14,960 twisted RegionServer connection lost (HOST:IPv4Address(TCP, '10.245.128.2', 48181) PEER:IPv4Address(TCP, '10.1.10.11', 51630))
INFO 2014-11-21 14:03:14,964 twisted RegionServer connection lost (HOST:IPv4Address(TCP, '10.245.128.2', 51702) PEER:IPv4Address(TCP, '10.1.10.11', 35831))
ERROR 2014-11-21 14:03:14,965 twisted Cluster '3ff52dfe-454b-4a91-bef5-5cc3bb111460' could not be authenticated; dropping connection.
Traceback (most recent call last):
Failure: twisted.internet.error.ConnectionDone: Connection was closed cleanly.

ERROR 2014-11-21 14:03:14,965 twisted Unhandled error in Deferred:
ERROR 2014-11-21 14:03:14,965 twisted Unhandled Error
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 1155, in gotResult
    _inlineCallbacks(r, g, deferred)
  File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 1145, in _inlineCallbacks
    deferred.errback()
  File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 423, in errback
    self._startRunCallbacks(fail)
  File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 490, in _startRunCallbacks
    self._runCallbacks()
--- <exception caught here> ---
  File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 577, in _runCallbacks
    current.result = callback(current.result, *args, **kw)
  File "/usr/lib/python2.7/dist-packages/maasserver/rpc/regionservice.py", line 426, in handshakeFailed
    return self.transport.loseConnection()
exceptions.AttributeError: 'NoneType' object has no attribute 'loseConnection'

description: updated
Changed in maas:
status: New → Triaged
importance: Undecided → Critical
milestone: none → 1.7.1
Changed in maas:
assignee: nobody → Blake Rouse (blake-rouse)
Revision history for this message
Blake Rouse (blake-rouse) wrote :

I have tested this with a fresh installation of MAAS 1.7. I disconnected the cluster, and I was able to import the images. All images imported correctly, but was still marked out-of-sync since the cluster was disconnected. This is the correct behavior.

I also tested this with 1.7.1rc1 and received the same result.

I am unable to reproduce this error.

Changed in maas:
status: Triaged → Incomplete
Changed in maas:
milestone: 1.7.1 → 1.7.2
Changed in maas:
milestone: 1.7.2 → 1.7.3
Changed in maas:
assignee: Blake Rouse (blake-rouse) → nobody
Changed in maas:
status: Incomplete → Invalid
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.