maas 2.1 fails deployment

Bug #1641171 reported by Mark W Wenning
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Invalid
Undecided
Unassigned
maas-cert-server
Fix Released
Critical
Jeff Lane 

Bug Description

Installed maas using directions in MANIACS document (this is for Certification).
Configured, connected to network.
Nodes enlisted fine,
Nodes commissioned fine. Told commission to enable ssh and stay powered on, verified network connectivity to MaaS server.
Told nodes to power off using MaaS gui, deployed

Nodes eventually hang without rebooting and display 'Deployment failed' on GUI.
Cannot ssh into nodes.
Cannot log into nodes from console. Console says "Ubuntu login:" instead of the name assigned by MaaS .

Posting video's of node deployment from console, plus requested logs.

Related branches

Revision history for this message
Mark W Wenning (mwenning) wrote :
Revision history for this message
Mark W Wenning (mwenning) wrote :
Revision history for this message
Mark W Wenning (mwenning) wrote :
Revision history for this message
Mark W Wenning (mwenning) wrote :
Revision history for this message
Mark W Wenning (mwenning) wrote :
Revision history for this message
Jeff Lane  (bladernr) wrote :

So the culprit was some code at the end of the curtin_userdata files that was left over from older MAAS versions. Removing those lines allows for successful deployments in 2.1.

Additionally, I tested it with Xenial and Trusty deployments on 2.0 and they were also successful.

Mike tried with Power and also deployed those successfully, so this seems to be good to go.

Changed in maas:
status: New → In Progress
status: In Progress → Invalid
Changed in maas-cert-server:
status: New → In Progress
importance: Undecided → Critical
assignee: nobody → Jeff Lane (bladernr)
Jeff Lane  (bladernr)
Changed in maas-cert-server:
status: In Progress → Fix Committed
Jeff Lane  (bladernr)
Changed in maas-cert-server:
status: Fix Committed → Fix Released
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.