maas commissioning api call fails silently if node is declared but powered on
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Won't Fix
|
Critical
|
Unassigned |
Bug Description
2015-08-14 20:50:56,331 DEBUG CMD: ['maas', 'admin', 'node', 'commission', u'node-
2015-08-14 20:50:56,598 DEBUG CMD: ['maas', 'admin', 'node', 'commission', u'node-
2015-08-14 20:50:56,859 DEBUG CMD: ['maas', 'admin', 'node', 'commission', u'node-
2015-08-14 20:50:57,122 DEBUG CMD: ['maas', 'admin', 'node', 'commission', u'node-
2015-08-14 20:50:57,390 DEBUG CMD: ['maas', 'admin', 'node', 'commission', u'node-
2015-08-14 20:50:57,653 DEBUG CMD: ['maas', 'admin', 'node', 'commission', u'node-
Apache Log gets the requests:
::1 - - [14/Aug/
::1 - - [14/Aug/
::1 - - [14/Aug/
::1 - - [14/Aug/
::1 - - [14/Aug/
::1 - - [14/Aug/
Maas log only shows one of these attempts:
Aug 14 20:50:57 maas maas.node: [INFO] C240-M4-3: Status transition from NEW to COMMISSIONING
Aug 14 20:50:58 maas maas.node: [INFO] C240-M4-3: Commissioning started
Notice, the 200 return on the maas API call, yet 5 of the calls are silently dropped. Here is an example of the api call on the command line:
2015-08-14 21:16:34,039 DEBUG CMD: ['maas', 'admin', 'node', 'commission', u'node-
2015-08-14 21:16:34,311 DEBUG STDOUT:
{
"ip_addresses": [
],
"cpu_count": 0,
"power_type": "ipmi",
"tag_names": [],
"swap_size": null,
"owner": null,
"macaddress
{
},
{
},
{
},
{
}
],
"zone": {
"name": "default",
},
"hostname": "C240-M4-4.gpod",
"storage": 0,
"system_id": "node-a7727e24-
"boot_type": "fastpath",
"memory": 0,
"disable_ipv4": false,
"status": 0,
"power_state": "on",
"routers": null,
"pxe_mac": null,
"netboot": true,
"osystem": "",
"substatus": 0,
"architecture": "amd64/generic",
"distro_
"resource_uri": "/MAAS/
}
Changed in maas: | |
status: | New → Triaged |
importance: | Undecided → Critical |
Changed in maas: | |
importance: | Critical → High |
Changed in maas: | |
importance: | High → Critical |
Dear user,
This is an automated message.
We believe this bug report is no longer an issue in the latest version of MAAS. For such reason, we are making this issue as Won't Fix. If you believe this issue is still present in the latest version of MAAS, please re-open this bug report.