NodeStateViolation when commissioning
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
High
|
Julian Edwards |
Bug Description
I started commissioning of a node, but it wasn't able to power on because amttool was not available, so I assume it tried to mark the node as broken/failed. I observed the following in maas-django.log
Traceback (most recent call last):
File "/usr/lib/
self.
File "/usr/lib/
self.run()
File "/usr/lib/
self.
--- <exception caught here> ---
File "/usr/lib/
result = context.call(ctx, function, *args, **kwargs)
File "/usr/lib/
return self.currentCon
File "/usr/lib/
return func(*args,**kw)
File "/usr/lib/
return func(*args, **kwargs)
File "/usr/lib/
return func(*args, **kwargs)
File "/usr/lib/
node.
File "/usr/lib/
self.status)
maasserver.
Related branches
- Jeroen T. Vermeulen (community): Approve
-
Diff: 32 lines (+11/-0)2 files modifiedsrc/maasserver/models/node.py (+3/-0)
src/maasserver/models/tests/test_node.py (+8/-0)
Changed in maas: | |
milestone: | none → 1.7.0 |
Changed in maas: | |
status: | In Progress → Fix Committed |
Changed in maas: | |
status: | Fix Committed → Fix Released |
Looks like 2 things were trying to mark the node as "failed". The first one succeeded and the node was transitioned to 'FAILED_ COMMISSIONING' . The second thing came along but the node couldn't be as "failed" because it was already marked "failed". Now, the stacktrace is not detailed enough to tell us precisely what this second thing was. AFAIK the only thing that can mark a node failed right now is the power code (when it fails to power up the node).