Failure: twisted.web.error.Error: 503 Service Unavailable

Bug #1436887 reported by Raphaël Badin
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
MAAS
Invalid
Wishlist
Unassigned

Bug Description

Just noticed that clusterd.log was full of errors like:

[HTTPPageGetter,client] Unhandled Error Traceback (most recent call last): Failure: twisted.web.error.Error: 503 Service Unavailable

There is very little indication as to the source of the problem. When this happened, I was trying to abort the commissioning of a bunch of nodes but it's hard to be sure this is the cause of the problem. Sorry about such an imprecise bug report but unfortunately the twisted crashes like this one appear asynchronously and don't give a lot of information about the problem… so I'm filing this as is so that we don't forget.

Tags: twisted
Gavin Panella (allenap)
description: updated
Changed in maas:
importance: Critical → High
Changed in maas:
importance: High → Critical
Revision history for this message
Mike Pontillo (mpontillo) wrote :

This happens when MAAS attempts to contact itself via HTTP via localhost, but an HTTP[s] proxy is configured. The workaround is to add the following to /etc/environment:

    no_proxy="localhost,127.0.0.1,::1"

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