Comment 5 for bug 1515188
Revision history for this message
| Mike Pontillo (mpontillo) wrote Re: [1.9] VmWare power management doesn't work with vm name | #5 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
I remember running into this when developing the power driver. Depending on the VMware API version, getting the VMs by name sometimes works and sometimes doesn't. That's why the option of getting the VM by UUID exists. (The "Add Hardware > Chassis" option tends to do the right thing and fill in the UUID during discovery.)
I think I implemented some code which will attempt to find the VM by name if the UUID is not available, and that's likely where you're seeing the bug. (Which version of VMware are python-pyvmomi are you using, and how exactly are the VMs organized in the system?)
If I can get access to the test environment, I could possibly come up with a fix/workaround. I do not have a license for vCenter to do my own testing. But I would need to know the following in order to reproduce the problem:
(1) Which version of VMware are you using, and which VMware product(s)?
(2) Which Ubuntu release is the cluster running, and which version of python[3]-pyvmomi is installed?
(3) How exactly are the VMs organized within VMware?