Bug #24501
closed
undefined method 'raw_networks" for <Fog::Computer::Vsphere::Real>
Description
I have been deploying VMWare images from a template for weeks on Katello / Foreman 16.2. Today I updated the OS and now every time I try to deploy a new VM it fails with undefined method `raw_networks' for #<Fog::Compute::Vsphere::Real:0x0000000fd65a60>. My setup is part of a POC and doesn't deploy from anything but an image, but the failure is happening immediately after VMWare has copied the template and told Foreman that the process has completed step 1.
foreman.noarch 1.16.2-1.el7
foreman-cli.noarch 1.16.2-1.el7
foreman-compute.noarch 1.16.2-1.el7
foreman-console.noarch 1.16.2-1.el7
foreman-debug.noarch 1.16.2-1.el7
foreman-installer.noarch 1:1.16.2-1.el7
foreman-installer-katello.noarch 3.5.2-1.el7
foreman-postgresql.noarch 1.16.2-1.el7
foreman-proxy.noarch 1.16.2-1.el7
foreman-release.noarch 1.16.2-1.el7
foreman-release-scl.noarch 3-1.el7
foreman-selinux.noarch 1.16.2-1.el7
foreman-vmware.noarch 1.16.2-1.el7
I do see that tfm-rubygem-fog-vsphere-2.3.0-1.el7.noarch was updated as part of the yum update today.
When I downgraded to the previous tfm-rubygem-fog-vsphere.noarch 0:2.1.1-2.el7.noarch, I no longer had the issue.
It appears that tfm-rubygem-fog-vsphere-2.3.0-1.el7.noarch has some issue communicating with VMWare that wasn't present in the older version.
Files
Updated by Tomer Brisker over 5 years ago
1.16 is no longer supported; However, looks like the 2.3 version of fog-vsphere was incorrectly added to the 1.16 repo and will be removed.
The workaround for this is to downgrade fog-vsphere to version 2.1.1.
Updated by Ewoud Kohl van Wijngaarden over 5 years ago
- Status changed from New to Resolved
fog-vsphere 2.3.0 has been removed from the yum repository. If it was installed you manually need to downgrade it but this prevents users from breaking their system with a yum update.