[2.2] If a single commissioning script times out, all scripts will enter "Timed out" state.
Bug #1679431 reported by
Mike Pontillo
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
High
|
Lee Trager |
Bug Description
In testing the commissioning script timeout branch[1], I noticed that if one of the scripts time out, *all* of them enter "Timed out" state.
I think that's a little misleading. They should probably enter "Aborted" state or some other state to indicate that they didn't run. Any script that *did* complete should not have its status modified. (not sure if this is the case already, since I tested a timeout with the very first script).
[1]:
https:/
Related branches
lp:~ltrager/maas/node_side_timeout
- Mike Pontillo (community): Approve
-
Diff: 1383 lines (+365/-138)14 files modifiedsrc/maasserver/static/partials/node-details.html (+6/-6)
src/maasserver/status_monitor.py (+9/-6)
src/maasserver/tests/test_status_monitor.py (+4/-4)
src/metadataserver/api.py (+3/-1)
src/metadataserver/enum.py (+2/-0)
src/metadataserver/models/scriptresult.py (+10/-7)
src/metadataserver/models/tests/test_scriptresult.py (+6/-0)
src/metadataserver/tests/test_api.py (+101/-70)
src/metadataserver/user_data/templates/snippets/maas_run_remote_scripts.py (+44/-10)
src/metadataserver/user_data/templates/snippets/tests/test_maas_run_remote_scripts.py (+42/-3)
src/provisioningserver/refresh/__init__.py (+34/-15)
src/provisioningserver/refresh/maas_api_helper.py (+38/-3)
src/provisioningserver/refresh/tests/test_maas_api_helper.py (+15/-2)
src/provisioningserver/refresh/tests/test_refresh.py (+51/-11)
Changed in maas: | |
milestone: | none → 2.2.0rc2 |
importance: | Undecided → High |
status: | New → Triaged |
Changed in maas: | |
importance: | High → Critical |
Changed in maas: | |
assignee: | nobody → Lee Trager (ltrager) |
status: | Triaged → In Progress |
importance: | Critical → High |
Changed in maas: | |
status: | In Progress → Fix Committed |
Changed in maas: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Script results are put into a timed out status in two ways, when the node status expires, and when any script goes past its own time out. Should scripts which are canceled by MAAS always be put into an aborted status?