Failed to query node's BMC - Power state could not be queried: 'in <string>' requires string as left operand, not bytes
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
Critical
|
Blake Rouse |
Bug Description
I see this error in the rackd.log a lot and errors checking the power state of all AMT-controller NUCs I have:
2016-04-13 15:39:57+0300 [ClusterClient,
Traceback (most recent call last):
File "/usr/lib/
File "/usr/lib/
File "/usr/lib/
File "/usr/lib/
--- <exception caught here> ---
File "/usr/lib/
result = result.
File "/usr/lib/
return g.throw(self.type, self.value, self.tb)
File "/usr/lib/
raise exc_type(
File "/usr/lib/
File "/usr/lib/
result = result.
File "/usr/lib/
return g.throw(self.type, self.value, self.tb)
File "/usr/lib/
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 self.amttool_
File "/usr/lib/
if b'S5' in output:
This MAAS was originally 1.9 on trusty, later upgraded to xenial and then the latest beta from the experimental3 PPA.
-------
maashw@
Desired=
| Status=
|/ Err?=(none)
||/ Name Version Architecture Description
+++-===
ii maas 2.0.0~beta2+
ii maas-cli 2.0.0~beta2+
rc maas-cluster-
ii maas-common 2.0.0~beta2+
ii maas-dhcp 2.0.0~beta2+
ii maas-dns 2.0.0~beta2+
ii maas-proxy 2.0.0~beta2+
ii maas-rack-
ii maas-region-api 2.0.0~beta2+
ii maas-region-
rc maas-region-
un python-django-maas <none> <none> (no description available)
un python-maas-client <none> <none> (no description available)
un python-
ii python3-django-maas 2.0.0~beta2+
ii python3-maas-client 2.0.0~beta2+
ii python3-
Related branches
- Mike Pontillo (community): Approve
- Newell Jensen (community): Approve
-
Diff: 427 lines (+45/-48)13 files modifiedsrc/provisioningserver/drivers/power/amt.py (+7/-4)
src/provisioningserver/drivers/power/apc.py (+2/-3)
src/provisioningserver/drivers/power/dli.py (+3/-3)
src/provisioningserver/drivers/power/ipmi.py (+2/-2)
src/provisioningserver/drivers/power/manual.py (+7/-10)
src/provisioningserver/drivers/power/moonshot.py (+1/-2)
src/provisioningserver/drivers/power/seamicro.py (+2/-2)
src/provisioningserver/drivers/power/tests/test_amt.py (+10/-9)
src/provisioningserver/drivers/power/tests/test_apc.py (+2/-3)
src/provisioningserver/drivers/power/tests/test_dli.py (+3/-3)
src/provisioningserver/drivers/power/tests/test_ipmi.py (+2/-2)
src/provisioningserver/drivers/power/tests/test_moonshot.py (+2/-3)
src/provisioningserver/drivers/power/tests/test_seamicro.py (+2/-2)
Changed in maas: | |
assignee: | nobody → Blake Rouse (blake-rouse) |
importance: | Undecided → Critical |
status: | New → In Progress |
Changed in maas: | |
status: | In Progress → Fix Committed |
Changed in maas: | |
status: | Fix Committed → Fix Released |
In case it might help, here's the output of `amtterm 10.14.0.11 info` for one of the nodes (issue happens with all nodes):
maashw@maas-hw:~$ amttool 10.14.0.11 info apabilities IDER SOL BiosSetup andsSupported PXE-boot HD-boot cd-boot ilitiesSupporte d powercycle powerdown powerup reset areCapabilities 7821
### AMT info on machine '10.14.0.11' ###
AMT version: 8.1.30
Hostname: node-11.maas
Powerstate: S5 (soft-off)
Remote Control Capabilities:
IanaOemNumber 157
OemDefinedC
SpecialComm
SystemCapab
SystemFirmw