Misleading error message in log "Unknown power_type 'sm15k'"

Bug #1381444 reported by Raphaël Badin
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
MAAS
Fix Released
High
Julian Edwards

Bug Description

When trying to query the power state of a node whose power type can't be queried, we get the following message:

Oct 15 09:56:49 maas-trusty-back-may22 maas.power: [ERROR] hayward-35: Failed to query power state: Unknown power_type 'sm15k'

The message is actually wrong, the power type is known but it can't be queried.

Related branches

tags: added: papercut power
Christian Reis (kiko)
Changed in maas:
milestone: none → next
Revision history for this message
Larry Michel (lmic) wrote :

These error message also happen for ucsm and ether-wake power types. It floads the log files as those queries happen quite often with a number of servers.

Oct 16 03:28:08 maas-trusty-back-may22 maas.power: [ERROR] pullman-01: Failed to query power state: Unknown power_type 'ucsm'.

Oct 16 14:50:33 maas-trusty-back-may22 maas.power: [ERROR] pullman-02-no-disk: Failed to query power state: Unknown power_type 'ether_wake'.

Changed in maas:
status: Triaged → In Progress
assignee: nobody → Julian Edwards (julian-edwards)
Sean Feole (sfeole)
tags: added: hs-arm64 hs-moonshot-maas-juju
Changed in maas:
status: In Progress → Fix Committed
Revision history for this message
Sean Feole (sfeole) wrote :

So i just tested maas 1.7 beta8 , I'm still seeing "Error: Unknown power_type 'mscm'" when checking nodes power state.

Revision history for this message
Sean Feole (sfeole) wrote :

here are the entries in /var/log/maas/maas.log

Oct 23 10:51:07 ubuntu maas.power: [ERROR] ms10-19-anders: Failed to query power state: Unknown power_type 'mscm'.
Oct 23 10:51:07 ubuntu maas.power: [ERROR] c5n1-avaton: Failed to query power state: Unknown power_type 'mscm'.
Oct 23 10:51:07 ubuntu maas.power: [ERROR] c39n1-mcdivitt: Failed to query power state: Unknown power_type 'mscm'.

Revision history for this message
Julian Edwards (julian-edwards) wrote :

The fix was not added to the 1.7 branch, it wasn't considered release critical.

Christian Reis (kiko)
Changed in maas:
milestone: next → 1.7.1
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.