Commission is not available because of the current state of the node.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
Medium
|
Lee Trager |
Bug Description
When using FCE, we wait for nodes to enlist and show up in NEW state, rename the machine, update some tags, then we issue a command to start commissioning.
That failed for one node in 2.5.0 rc2 with this error:
2018-12-11-08:55:49 root DEBUG maas root machines read
2018-12-11-08:55:53 root DEBUG maas root machine power-parameters nprfpk
2018-12-11-08:55:55 foundationcloud
2018-12-11-08:55:55 root DEBUG maas root machine update nprfpk hostname=geodude zone=default
2018-12-11-08:55:58 root DEBUG maas root tag read foundation-nodes
2018-12-11-08:56:00 root DEBUG maas root tag update-nodes foundation-nodes add=nprfpk
2018-12-11-08:56:02 root DEBUG maas root machine commission nprfpk
2018-12-11-08:56:05 root ERROR Command failed: machine commission nprfpk
2018-12-11-08:56:05 root ERROR {"__all__": ["Commission is not available because of the current state of the node."]}
At 2018-12-11-08:55:49 the machine was in NEW state. We didn't issue any commission commands until 2018-12-
According to the maas logs, it looks like after we read NEW state and before we started commissioning, the machine transitioned to COMMISSIONING state on its own without us telling it to:
10.244.
This is with 2.5.0~rc2-
Related branches
- Lee Trager (community): Approve
-
Diff: 455 lines (+118/-26)12 files modifiedsrc/maasserver/api/machines.py (+19/-6)
src/maasserver/api/tests/test_enlistment.py (+22/-3)
src/maasserver/forms/__init__.py (+23/-0)
src/maasserver/forms/settings.py (+11/-0)
src/maasserver/forms/tests/test_machine.py (+2/-0)
src/maasserver/forms/tests/test_machinewithmacaddresses.py (+17/-1)
src/maasserver/models/config.py (+2/-0)
src/metadataserver/api.py (+6/-6)
src/metadataserver/tests/test_api.py (+0/-4)
src/metadataserver/user_data/templates/enlistment.template (+5/-1)
src/metadataserver/user_data/templates/snippets/maas_enlist.sh (+9/-4)
src/metadataserver/user_data/tests/test_generate_user_data.py (+2/-1)
- Jason Hobbs (community): Approve
- MAAS Lander: Approve
- Mike Pontillo (community): Approve
- Spencer Seidel (community): Needs Information
- Andres Rodriguez (community): Needs Information
-
Diff: 455 lines (+118/-26)12 files modifiedsrc/maasserver/api/machines.py (+19/-6)
src/maasserver/api/tests/test_enlistment.py (+22/-3)
src/maasserver/forms/__init__.py (+23/-0)
src/maasserver/forms/settings.py (+11/-0)
src/maasserver/forms/tests/test_machine.py (+2/-0)
src/maasserver/forms/tests/test_machinewithmacaddresses.py (+17/-1)
src/maasserver/models/config.py (+2/-0)
src/metadataserver/api.py (+6/-6)
src/metadataserver/tests/test_api.py (+0/-4)
src/metadataserver/user_data/templates/enlistment.template (+5/-1)
src/metadataserver/user_data/templates/snippets/maas_enlist.sh (+9/-4)
src/metadataserver/user_data/tests/test_generate_user_data.py (+2/-1)
Changed in maas: | |
status: | Triaged → Fix Committed |
Changed in maas: | |
status: | Fix Committed → Fix Released |
MAAS run's commissioning during enlistment. This means that the machine will:
1. Register itself to MAAS
2. After registering, the machine will start the commissioning process
3. Once they are commissioned, the machine will be set to 'New'.
To move from 'New' to ready you have two options:
1. Commission again
2. Test hardware.