[2.3, HA] Machines fails commissioning and testing and MAAS shows no errors
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Invalid
|
Critical
|
Unassigned | ||
Bug Description
I start the commissioning of a machine, it starts running all commissioning scripts just fine, however, it gets stuck at a certain point.
When it gets to "00-maas-
I then access the machine remotely, and check cloud-init.log and see the following error. Note that this is hardware that was previously commissioned and working fine on older versions of MAAS.
request to http://
request to http://
request to http://
request to http://
request to http://
request to http://
request to http://
FAIL: HTTP error [400]
| description: | updated |
| Changed in maas: | |
| importance: | Undecided → Critical |
| milestone: | none → 2.3.0beta3 |
| status: | New → Triaged |
| Mike Pontillo (mpontillo) wrote | #1 |
| Andres Rodriguez (andreserl) wrote | #2 |
| Changed in maas: | |
| status: | Triaged → Invalid |
I think this is technically a duplicate of bug #1718517 (that is, the fix I'm planning on landing for that issue should address the "shows no errors" concern), but I'll leave it open because this means there's an issue with the post-processing of commissioning output - probably related to the post-processing of block devices.
Once the fix for #1718517 lands, it will be easier to troubleshoot that issue, since the output from the block devices script will be properly stored in the database.