Internal Server Error if ti cannot connect to the Cluster

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

Bug Description

While the cluster was disconnected, I tried to change it from Enabled to Disable and an "Internal Server Error" was shown:

=> /var/log/maas/regiond.log <==
     return func(*args, **kwargs)
   File "/usr/lib/python2.7/dist-packages/maasserver/utils/async.py", line 180, in fire
     self._fire_in_reactor(hook).wait()
   File "/usr/lib/python2.7/dist-packages/crochet/_eventloop.py", line 219, in wait
     result.raiseException()
   File "<string>", line 2, in raiseException

 provisioningserver.rpc.exceptions.NoConnectionsAvailable: Unable to connect to cluster a7f0d619-63eb-4460-9e27-71c79561c0a0; no connections available.

Changed in maas:
milestone: none → 1.9.0
importance: Undecided → Critical
status: New → Triaged
Christian Reis (kiko)
Changed in maas:
importance: Critical → High
importance: High → Medium
milestone: 1.9.0 → 1.9.1
Changed in maas:
milestone: 1.9.1 → 1.9.2
Changed in maas:
milestone: 1.9.2 → 1.9.3
no longer affects: maas/1.8
Changed in maas:
milestone: 1.9.3 → 1.9.4
Changed in maas:
milestone: 1.9.4 → 1.9.5
Revision history for this message
Andres Rodriguez (andreserl) wrote :

We believe that this is not longer an issue in the latest releases of MAAS. If you believe this is still an issue, please re-open this bug report and target it accordingly.

Changed in maas:
status: Triaged → 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.