Bug #3072
closed
Vmware: error listing VMs
Added by Angelo Lisco about 11 years ago.
Updated about 11 years ago.
Category:
Compute resources
|
|
Description
After adding a compute resource (vsphere 5.1.0) in foreman-nighly, I get this error trying to browse the virtual machines:
"There was an error listing VMs: undefined method `state' for #<FogExtensions::Vsphere::MiniServer:0x000000081fa538>"
System information:
Red Hat Enterprise 6.4 (x86_84)
Packages:
foreman-compute-1.2.9999-10.201309102143gitbc89eb3.el6.noarch
foreman-assets-1.2.9999-10.201309102143gitbc89eb3.el6.noarch
rubygem-foreman_api-0.1.6-1.el6.noarch
foreman-release-1.2.9999-9.201309091013git2b15ea6.el6.noarch
ruby193-rubygem-foremancli-1.0-6.el6.noarch
foreman-1.2.9999-10.201309102143gitbc89eb3.el6.noarch
foreman-vmware-1.2.9999-10.201309102143gitbc89eb3.el6.noarch
foreman-postgresql-1.2.9999-10.201309102143gitbc89eb3.el6.noarch
foreman-sqlite-1.2.9999-10.201309102143gitbc89eb3.el6.noarch
foreman-installer-1.2.9999-3.201309061614gite83c8c6.el6.noarch
foreman-cli-1.2.9999-10.201309102143gitbc89eb3.el6.noarch
foreman-proxy-1.3.9999-1.201309091626git296617a.el6.noarch
- Target version set to 1.3.0
Regression from 1.2 I think.
So the target 1.3 means - we will focus on that and try to get it into 1.3 I guess. Okay.
Dominic Cleal wrote:
Regression from 1.2 I think.
Thank you Dominic for raising the importance of this bug.
Maybe it's a 'fog' regression from 1.2?
Probably a regression due to us improving the power state support, maybe the vSphere provider doesn't expose the same methods.
- Priority changed from Normal to Urgent
I'm getting this too and happy to test when fixes available. I'm running against the katello-foreman repo though, so may be behind your efforts?
- Status changed from New to Ready For Testing
- Assignee set to Martin Matuška
https://github.com/theforeman/foreman/pull/893
There's a patch you can try on there Duncan, or nightly builds will be published to the Foreman yum repos later today after it's merged. Katello repos are refreshed from ours every few weeks I think.
- Priority changed from Urgent to Immediate
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied patch(es) manually. Error is gone, but I only get 1 vGuest reporting back out of 232. Possibly my configuration?
- Related to Tracker #3112: [TRACKER] Issues to be released in 1.3 RC or final added
The patch works and i'm able to connect to our Vsphere infrastructure but I still can't see all the deployed vm's. I noticed that all the vms which are located in a 'vmware directory' are not visible.
Maybe it's another bug?
The folders issue is tracked in #2093, possibly that's what's causing Duncan's issue too.
Yes - the server I'm listing is the only one not in a folder. Great. Will wait the resolution of #2093
Actually, is there any way of poking #2093 up the priority list a bit? I've commented on it, but it looks unloved for a while. I've not worked on a site where VM folders are not used in some way, so this is a bigger issue than perhaps perceived at present.
If you can complete the attached patch and submit it, we can get it included in a future release. There's more information available on the website on getting started in the project (-dev IRC and mailing lists are also useful resources).
- Related to deleted (Tracker #3112: [TRACKER] Issues to be released in 1.3 RC or final)
- Has duplicate Bug #4057: Foreman won't load VM's from vSphere 5 added
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
Updated by