Can't create node in the UI with 1.7 beta 4

Bug #1375835 reported by Jeroen T. Vermeulen
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
MAAS
Fix Released
Critical
Graham Binns

Bug Description

I've got a virtual machine running 1.7 beta 4 on Trusty, upgraded from a fresh 1.5 install. I think I've imported at least some portion of my images, because the Node add/edit form shows an architecture choice (although there's still a spinner on the Images page).

When I try to create a node through the UI (it doesn't really exist), I get this error at the top of the “Add node” page:

«Unable to create Node: Unrecognised signature: GET None»

Related branches

Revision history for this message
Jeroen T. Vermeulen (jtv) wrote :

Exact version of the package is 1.7.0~beta4+bzr3130-0ubuntu1~trusty1

Revision history for this message
Raphaël Badin (rvb) wrote :

Might be related to bug 1375834 (although the error you're getting is different from the one mentioned on this bug).

Revision history for this message
Jeroen T. Vermeulen (jtv) wrote :

Ah. The log shows that the server tries to start commissioning on the node I created (and which doesn't actually exist):

«
Sep 30 14:43:26 test-1 maas.api: [INFO] afdsddghy: Enlisted new node
Sep 30 14:43:26 test-1 maas.node: [INFO] afdsddghy: Starting commissioning
»

Yet the UI suggests that I never enlisted the node. I never got past the form, and the nodes listing doesn't show the thing.

Graham Binns (gmb)
Changed in maas:
status: Triaged → In Progress
assignee: nobody → Graham Binns (gmb)
Changed in maas:
status: In Progress → Fix Committed
Changed in maas:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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