UI reports incorrect status for enlisting nodes
Bug #1886866 reported by
Nick Niehoff
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Triaged
|
Low
|
Unassigned | ||
Bug Description
When a new machine is PXE booted and it enters the enlisting phase, MAAS adds the machine but reports the status as commissioning instead of enlisting. Once complete the machine goes to the new state forcing the machine to then be commissioned. The status should reflect the enlisting phase when the machine is enlisting.
Revision history for this message
| Lee Trager (ltrager) wrote | #1 |
| Changed in maas: | |
| importance: | Undecided → Wishlist |
| Changed in maas: | |
| status: | New → Triaged |
| Changed in maas: | |
| importance: | Wishlist → Low |
| milestone: | none → 3.4.0 |
| Changed in maas: | |
| milestone: | 3.4.0 → 3.4.x |
To post a comment you must log in.
There actually is no enlisting status in MAAS. Its a term we use to describe a machine that is added to MAAS by being powered on and automatically network booted. Originally a machine being enlisted would be added as a new machine. A few years ago I added a feature to commission a machine when being enlisted. During discussion of this feature it was agreed that it should go through the normal commissioning process and then revert back to a new state to force an administrator to accept it.
Creating a new status for enlistment would require a bit of backend work as the code looks for the commissioning status and uses "commissioning" in logging and other areas. We may want to discuss a better way to tell users the machine is being enlisted without creating a new status.