1.8.X - Internal Server Error when trying to configure a cluster interface on wily

Bug #1504971 reported by Andres Rodriguez on 2015-10-11
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Critical
LaMont Jones
Twisted
Unknown
Unknown
twisted (Ubuntu)
Undecided
Unassigned

Bug Description

Trying to configure a cluster interface in wily yileds the following (This is using MAAs 1.8.3 proposed in Wily):

==> /var/log/maas/regiond.log <==
2015-10-11 09:10:21 [HTTPChannel,0,127.0.0.1] 500 Error - /MAAS/clusters/0f1d0fdb-049d-493e-bbd8-076442262f79/interfaces/virbr0/edit/
        Traceback (most recent call last):
          File "/usr/lib/python2.7/dist-packages/twisted/web/wsgi.py", line 315, in run
            appIterator = self.application(self.environ, self.startResponse)
          File "/usr/lib/django16/django/core/handlers/wsgi.py", line 206, in __call__
            response = self.get_response(request)
          File "/usr/lib/python2.7/dist-packages/maasserver/utils/views.py", line 213, in get_response
            response = get_response(request)
          File "/usr/lib/python2.7/dist-packages/maasserver/utils/views.py", line 202, in get_response
            request, get_resolver(None), sys.exc_info())
        --- <exception caught here> ---
          File "/usr/lib/python2.7/dist-packages/maasserver/utils/views.py", line 187, in get_response
            return django_get_response(request)
          File "/usr/lib/python2.7/dist-packages/maasserver/utils/orm.py", line 331, in __exit__
            self.fire()
          File "/usr/lib/python2.7/dist-packages/provisioningserver/utils/twisted.py", line 154, in wrapper
            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.CannotConfigureDHCP: DHCPv6 server failed to stop: Unable to parse the active state from systemd for service 'maas-dhcpd6', active state reported as 'failed'.

Related branches

Andres Rodriguez (andreserl) wrote :

This probably affects trunk

Changed in maas:
milestone: none → 1.8.3
importance: Undecided → Critical
summary: - Internal Server Error when trying to configure a cluster interface
+ 1.8.X - Internal Server Error when trying to configure a cluster
+ interface
summary: 1.8.X - Internal Server Error when trying to configure a cluster
- interface
+ interface on wily
Changed in maas:
status: New → Triaged
Changed in maas:
assignee: nobody → Mike Pontillo (mpontillo)
Changed in maas:
assignee: Mike Pontillo (mpontillo) → LaMont Jones (lamont)
LaMont Jones (lamont) wrote :

This is actually a regression related to twisted package changes and bug #1372767 - which was fixed in maas instead of twisted. Filed 1505748 so that we can eventually stop maintaining a fork of one function in twisted.

Changed in maas:
status: Triaged → In Progress
Andres Rodriguez (andreserl) wrote :

So what's the proposed fix for this? We need to make sure this works for all trusty, vivid, wily

LaMont Jones (lamont) wrote :

The fix (for now) is to adjust our bug 1372767 fix to handle twisted.web.client having either _URI or URI as a class. Ultimately, it means that we deal with the name change in 2 places. See also https://code.launchpad.net/~lamont/maas/bug-1504971/+merge/274290 -- ultimately changed to be similar to the fix in trunk (1.9).

Once bug 1505748 is fixed in every release we support, we can revisit the fix to drop it entirely. That is flagged in the source.

Changed in maas:
status: In Progress → Fix Committed
Matthias Klose (doko) wrote :

apparently known upstream for Twisted

Changed in twisted (Ubuntu):
status: New → Confirmed
Matthias Klose (doko) wrote :

fixed in the twisted package in wily

Changed in twisted (Ubuntu):
status: Confirmed → Fix Released
Changed in maas:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.