[2.4] UpdateNodePowerState RPC calls causes "Must be one of the node's interfaces."
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
Critical
|
Blake Rouse |
Bug Description
This to me seem like performance issues with the RPC communication. MAAS has 100 machines, while commissioning about 40.
Ok, so this is interesting:
1. The machine got added but seems that it doesn't have an interface attached (e.g MAAS failed to add the interface of the machine)
2. The machine is in 'commissioning' state, and cannot be aborted with the same message.
2018-02-16 15:44:56 provisioningser
mand. [autopkgtest:
Traceback (most recent call last):
File "/usr/lib/
File "/usr/lib/
File "/usr/lib/
File "/usr/lib/
--- <exception caught here> ---
File "/usr/lib/
File "/usr/lib/
key = error.trap(
File "/usr/lib/
File "/usr/lib/
raise self.value.
File "/usr/lib/
result = inContext.theWork()
File "/usr/lib/
File "/usr/lib/
return self.currentCon
File "/usr/lib/
return func(*args,**kw)
File "/usr/lib/
return func(*args, **kwargs)
File "/usr/lib/
result = func(*args, **kwargs)
File "/usr/lib/
return func_outside_
File "/usr/lib/
return func(*args, **kwargs)
File "/usr/lib/
return func(*args, **kwds)
File "/usr/lib/
File "/usr/lib/
return func_within_
File "/usr/lib/
return func(*args, **kwds)
File "/usr/lib/
File "/usr/lib/
File "/usr/lib/
File "/usr/lib/
raise ValidationError
Changed in maas: | |
milestone: | none → 2.4.0alpha2 |
importance: | Undecided → Critical |
description: | updated |
Changed in maas: | |
status: | New → Triaged |
assignee: | nobody → Blake Rouse (blake-rouse) |
tags: | added: performance |
description: | updated |
description: | updated |
Changed in maas: | |
milestone: | 2.4.0alpha2 → 2.4.0beta1 |
Changed in maas: | |
status: | Fix Committed → Fix Released |
With the change made to only update and validate the fields that have changed, this is not longer an issue.