Comment 13 for bug 1611999
Revision history for this message
| jeffrey leung (jefleung) wrote Re: [2.0] MAAS cannot power query with Cisco UCSM power driver | #13 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
Hi,
I opened up a bug on Cisco's end to check this out. There was a misunderstanding of the XML model on our part initially but after working with development we found that when MAAS checks the power status, it was querying the wrong attribute. When power is changed by UCSM, we call that the Desired Power State. I've attached a screenshot where you can see from the status of a Service Profile under the Servers tab after commissioning was finished on a new node.
The desired power state never changed after MAAS uses UCSM to power on and commission but issues the shutdown through the OS. This is why when we tried to check the power status through MAAS, it still returns with Power On despite overall status in UCSM shows Power Off.
Continue to use lsPower for controlling the power state, but to check the actual power status it's recommended to use the operState under the lsServer classID. I copied the XML from a service profile with the issue and the lsPower state was still up, but the lsServer operState showed as powered off:
lsServer
operState=
-Jeff