[doc] commission does not fail NEW nodes
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
Medium
|
Bill Wear |
Bug Description
MAAS 2.5 documentation says: "A machine in the 'ready', 'declared' or 'failed test' state may initiate a commissioning cycle where it is checked out and tested in preparation for transitioning to the 'ready' state. If it is already in the 'ready' state this is considered a re-commissioning process which is useful if commissioning tests were changed after it previously commissioned."
=======
But both the CLI and the restful API are allowing "NEW" as well, in both MAAS 2.4 and 2.5
Unclear if this is "just" a documentation issue, or if there is a failure to enforce a constraint. Personally, I don't see why NEW isn't listed as a valid state for this API.
steps:
1) locate a node in the NEW state (say s3aq7d)
2) Use API to commission
POST /MAAS/api/
Host: 100.80.70.8:5240
Accept: application/json
cache-control: no-cache
Postman-Token: 19c486d8-
3) Observe success
summary: |
- commission does not fail NEW nodes + [doc] commission does not fail NEW nodes |
Changed in maas: | |
milestone: | 2.5.1 → 2.5.2 |
Changed in maas: | |
milestone: | 2.5.2 → 2.5.3 |
Changed in maas: | |
milestone: | 2.5.3 → 2.5.4 |
Changed in maas: | |
milestone: | 2.5.4 → none |
Changed in maas: | |
milestone: | none → 2.9.x |
Changed in maas: | |
milestone: | 2.9.2 → 2.9.x |
Changed in maas: | |
status: | Incomplete → Triaged |
Changed in maas: | |
milestone: | 2.9.x → none |
and MAAS 2.3 0ubuntu1)
MAAS version: 2.3.5 (6511-gf466fdb-