Digital Logers Power Type Fails Power On

Bug #1557030 reported by Ryan Collis
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Fix Released
High
Newell Jensen
1.9
Fix Released
High
Newell Jensen

Bug Description

[Xenial + MAAS 2.0-Alpha2+bzr4776] After manually enlisting our APM systems and applying the Digital Loggers power type, nodes are unable to be powered on for commissioning (state changes to failed commissioning within seconds). The interesting thing is that the nodes if powered on manually can be powered off from the MAAS ui with no issue.

Power On Error From MAAS ui
"Failed to power on node - Node could not be powered on: Failed talking to node's BMC for an unknown reason."

Log Entry From Digital Loggers PDU
Mar 14 10:51:18 ps7[1946339]: Successful basic HTTP authentication for .PDU_USERNAME. from 172.x.x.x

There does not appear to be anything present in the maas logs relating to this issue.

dpkg -l '*maas*'|cat
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-===============================-=====================================-============-=============================================
ii maas 2.0.0~alpha2+bzr4776-0ubuntu1~xenial1 all MAAS server all-in-one metapackage
ii maas-cli 2.0.0~alpha2+bzr4776-0ubuntu1~xenial1 all MAAS command line API tool
ii maas-common 2.0.0~alpha2+bzr4776-0ubuntu1~xenial1 all MAAS server common files
ii maas-dhcp 2.0.0~alpha2+bzr4776-0ubuntu1~xenial1 all MAAS DHCP server
ii maas-dns 2.0.0~alpha2+bzr4776-0ubuntu1~xenial1 all MAAS DNS server
ii maas-proxy 2.0.0~alpha2+bzr4776-0ubuntu1~xenial1 all MAAS Caching Proxy
ii maas-rack-controller 2.0.0~alpha2+bzr4776-0ubuntu1~xenial1 all MAAS server cluster controller
ii maas-region-controller 2.0.0~alpha2+bzr4776-0ubuntu1~xenial1 all MAAS server complete region controller
ii maas-region-controller-min 2.0.0~alpha2+bzr4776-0ubuntu1~xenial1 all MAAS Server minimum region controller
ii python3-django-maas 2.0.0~alpha2+bzr4776-0ubuntu1~xenial1 all MAAS server Django web framework (Python 3)
ii python3-maas-client 2.0.0~alpha2+bzr4776-0ubuntu1~xenial1 all MAAS python API client (Python 3)
ii python3-maas-provisioningserver 2.0.0~alpha2+bzr4776-0ubuntu1~xenial1 all MAAS server provisioning libraries (Python 3)

Related branches

Revision history for this message
Andres Rodriguez (andreserl) wrote :

Hi there,

CAn you please attach lgos fro /var/log/maas/*.log

Changed in maas:
milestone: none → 2.0.0
importance: Undecided → High
Revision history for this message
Ryan Collis (vyan) wrote :
Download full text (5.5 KiB)

Cleared Logs and tried to commission APM nodes. Log entries below.

rackd.log
2016-03-14 12:19:39-0400 [ClusterClient,client] strata: Power could not be turned on.
 Traceback (most recent call last):
   File "/usr/lib/python3/dist-packages/twisted/internet/defer.py", line 393, in callback
     self._startRunCallbacks(result)
   File "/usr/lib/python3/dist-packages/twisted/internet/defer.py", line 501, in _startRunCallbacks
     self._runCallbacks()
   File "/usr/lib/python3/dist-packages/twisted/internet/defer.py", line 588, in _runCallbacks
     current.result = callback(current.result, *args, **kw)
   File "/usr/lib/python3/dist-packages/twisted/internet/defer.py", line 1184, in gotResult
     _inlineCallbacks(r, g, deferred)
 --- <exception caught here> ---
   File "/usr/lib/python3/dist-packages/twisted/internet/defer.py", line 1126, in _inlineCallbacks
     result = result.throwExceptionIntoGenerator(g)
   File "/usr/lib/python3/dist-packages/twisted/python/failure.py", line 389, in throwExceptionIntoGenerator
     return g.throw(self.type, self.value, self.tb)
   File "/usr/lib/python3/dist-packages/provisioningserver/power/change.py", line 251, in change_power_state
     system_id, hostname, power_type, power_change, context)
   File "/usr/lib/python3/dist-packages/twisted/internet/defer.py", line 1126, in _inlineCallbacks
     result = result.throwExceptionIntoGenerator(g)
   File "/usr/lib/python3/dist-packages/twisted/python/failure.py", line 389, in throwExceptionIntoGenerator
     return g.throw(self.type, self.value, self.tb)
   File "/usr/lib/python3/dist-packages/provisioningserver/drivers/power/__init__.py", line 270, in perform_power
     power_func, system_id, context)
   File "/usr/lib/python3/dist-packages/twisted/python/threadpool.py", line 246, in inContext
     result = inContext.theWork()
   File "/usr/lib/python3/dist-packages/twisted/python/threadpool.py", line 262, in <lambda>
     inContext.theWork = lambda: context.call(ctx, func, *args, **kw)
   File "/usr/lib/python3/dist-packages/twisted/python/context.py", line 118, in callWithContext
     return self.currentContext().callWithContext(ctx, func, *args, **kw)
   File "/usr/lib/python3/dist-packages/twisted/python/context.py", line 81, in callWithContext
     return func(*args,**kw)
   File "/usr/lib/python3/dist-packages/provisioningserver/drivers/power/dli.py", line 91, in power_on
     if self._query_outlet_state(**context) == 'on':
   File "/usr/lib/python3/dist-packages/provisioningserver/drivers/power/dli.py", line 75, in _query_outlet_state
     state = query.split('<!-- state=')[1].split()[0]
 builtins.TypeError: a bytes-like object is required, not 'str'

2016-03-14 12:21:51-0400 [ClusterClient,client] strata: Power could not be turned on.
 Traceback (most recent call last):
   File "/usr/lib/python3/dist-packages/twisted/internet/defer.py", line 393, in callback
     self._startRunCallbacks(result)
   File "/usr/lib/python3/dist-packages/twisted/internet/defer.py", line 501, in _startRunCallbacks
     self._runCallbacks()
   File "/usr/lib/python3/dist-packages/twisted/internet/defer.py", line 588, in _runCallbacks
     current.result = callback(curre...

Read more...

Changed in maas:
assignee: nobody → Newell Jensen (newell-jensen)
status: New → Incomplete
status: Incomplete → Triaged
Changed in maas:
status: Triaged → In Progress
Changed in maas:
status: In Progress → Fix Committed
Revision history for this message
Ryan Collis (vyan) wrote :

Not sure if I have this right. Should the fix for this be implemented in maas 2.0 beta? We are still experiencing the same issue as above with the exact same error in the logs. I apologize if this hasn't been implemented yet.

Revision history for this message
Newell Jensen (newell-jensen) wrote :

Ryan,

Are you sure you are running the changes that the linked branch has for dli.py? This is not fix released yet so it not part of a current release.

Changed in maas:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.