[2.1] Rack failed to run/register on fresh install

Bug #1624693 reported by Andres Rodriguez
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Won't Fix
Critical
Unassigned

Bug Description

2016-09-17 12:20:50 [ClusterClient,client] Failed to update and/or record network interface configuration: (b'UNHANDLED', 'Unknown Error [unleashed:pid=29417:cmd=RequestRackRefresh:ask=3]')
        Traceback (most recent call last):
        Failure: twisted.protocols.amp.UnhandledCommand: (b'UNHANDLED', 'Unknown Error [unleashed:pid=29417:cmd=RequestRackRefresh:ask=3]')

2016-09-17 12:21:20 [ClusterClient,client] Failed to update and/or record network interface configuration: (b'UNHANDLED', 'Unknown Error [unleashed:pid=29419:cmd=RequestRackRefresh:ask=5]')
        Traceback (most recent call last):
        Failure: twisted.protocols.amp.UnhandledCommand: (b'UNHANDLED', 'Unknown Error [unleashed:pid=29419:cmd=RequestRackRefresh:ask=5]')

2016-09-17 12:21:20 [ClusterClient,client] Failed to monitor services and update region.
        Traceback (most recent call last):
          File "/usr/lib/python3/dist-packages/twisted/internet/defer.py", line 434, in errback
            self._startRunCallbacks(fail)
          File "/usr/lib/python3/dist-packages/twisted/internet/defer.py", line 501, in _startRunCallbacks
            self._runCallbacks()
          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)
        --- <exception caught here> ---
          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)
          File "/usr/lib/python3/dist-packages/provisioningserver/rackdservices/service_monitor_service.py", line 95, in _updateRegion
            services=services)
        provisioningserver.rpc.exceptions.NoSuchCluster: The cluster with UUID fyx487 could not be found.

Revision history for this message
Andres Rodriguez (andreserl) wrote :

I then manually restarted maas-rackd and saw:

2016-09-17 12:29:17 [ClusterClient,client] Rack controller 'fyx487' registered (via unleashed:pid=29419).

==> /var/log/maas/maas.log <==
Sep 17 12:29:17 unleashed maas.interface: [WARNING] While adding virbr0 (bridge) on unleashed: found a MAC address already in use by virbr1 (bridge) on
 unleashed.
Sep 17 12:29:17 unleashed maas.interface: [WARNING] While adding virbr0 (bridge) on unleashed: found a MAC address already in use by virbr1 (bridge) on
 unleashed.
Sep 17 12:29:17 unleashed maas.interface: [WARNING] While adding virbr0 (bridge) on unleashed: found a MAC address already in use by virbr1 (bridge) on
 unleashed.

==> /var/log/maas/regiond.log <==
2016-09-17 12:29:17 [-] Successfully configured DNS.

==> /var/log/maas/maas.log <==
Sep 17 12:29:17 unleashed maas.interface: [WARNING] While adding virbr1 (bridge) on unleashed: found a MAC address already in use by virbr2 (bridge) on
 unleashed.

==> /var/log/maas/regiond.log <==
2016-09-17 12:29:17 [-] ::ffff:127.0.0.1 - - [17/Sep/2016:16:29:17 +0000] "GET /MAAS/rpc/ HTTP/1.0" 200 1804 "-" "provisioningserver.rpc.clusterservice.ClusterClientService"

==> /var/log/maas/maas.log <==
Sep 17 12:29:17 unleashed maas.interface: [WARNING] While adding virbr1 (bridge) on unleashed: found a MAC address already in use by virbr2 (bridge) on unleashed.
Sep 17 12:29:17 unleashed maas.interface: [WARNING] While adding virbr1 (bridge) on unleashed: found a MAC address already in use by virbr2 (bridge) on unleashed.
Sep 17 12:29:17 unleashed maas.interface: [WARNING] While adding virbr2 (bridge) on unleashed: found a MAC address already in use by virbr1 (bridge) on unleashed.
Sep 17 12:29:17 unleashed maas.interface: message repeated 2 times: [ [WARNING] While adding virbr2 (bridge) on unleashed: found a MAC address already
in use by virbr1 (bridge) on unleashed.]
Sep 17 12:29:17 unleashed maas.interface: [WARNING] While adding virbr3 (bridge) on unleashed: found a MAC address already in use by virbr1 (bridge) on
 unleashed.
Sep 17 12:29:17 unleashed maas.interface: message repeated 2 times: [ [WARNING] While adding virbr3 (bridge) on unleashed: found a MAC address already
in use by virbr1 (bridge) on unleashed.]
Sep 17 12:29:18 unleashed maas.rpc.rackcontrollers: [INFO] Registering existing rack controller 'unleashed'.

==> /var/log/maas/regiond.log <==
2016-09-17 12:29:18 [-] Rack controller 'fyx487' has been registered.

Changed in maas:
milestone: none → 2.1.0
importance: Undecided → Critical
Gavin Panella (allenap)
Changed in maas:
status: New → Triaged
Changed in maas:
status: Triaged → Incomplete
Changed in maas:
milestone: 2.1.0 → 2.1.1
Changed in maas:
milestone: 2.1.1 → 2.1.2
Changed in maas:
milestone: 2.1.2 → 2.1.3
Revision history for this message
Andres Rodriguez (andreserl) wrote :

Dear user,

This is an automated message.

We believe this bug report is no longer an issue in the latest version of MAAS. For such reason, we are making this issue as Won't Fix. If you believe this issue is still present in the latest version of MAAS, please re-open this bug report.

Changed in maas:
status: Incomplete → Won't Fix
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.