Hello,
I’m trying to install VMs from foreman and getting this error:
undefined method `raw_networks’ for #Fog::Compute::Vsphere::Real:0x007f4eb145e690
I see that VM is created in Vcenter, but powered off.
Any ideas?
Thanks
Which fog-vsphere library are you using? There was a update to 2.3.0 recently.
tfm-rubygem-fog-vsphere.noarch 0:2.3.0-1.el7
Downgraded to 2.1 - this’s fixed the issue,
Thanks!
Well, on 1.16.2 with 2.3.0 foreman throws an error I mentioned and provision breaks.
Yeah, I know. You either need to downgrade or use the patch I linked above.
Looks like the fix hasn’t been cherry picked to any of the released versions yet, i’m looking into this.
The fog-vsphere 2.3 rpm was mistakenly built into the 1.16 repo, which causes this failure on rpm based installs of Foreman 1.16. This has also been reported on redmine: Bug #24501: undefined method 'raw_networks" for <Fog::Computer::Vsphere::Real> - Foreman
An additional problem is present in debian installs, which pull in the 2.3 gem due to bundling dependencies at build time.
I have opened PRs to pull in the fixes to the stable branches:
theforeman:1.17-stable
← tbrisker:117-vmware
opened 11:23AM - 06 Aug 18 UTC
<!---
Thank you for contributing to The Foreman, please read the
[following … guide](https://www.theforeman.org/contribute.html), in short:
* [Create an issue](https://projects.theforeman.org/projects/foreman/issues)
* Reference the issue via `Fixes #1234` in the commit message
* Prefer present-tense, imperative-style commit messages
* Mark all strings for translation, see [Translating section in the guide]
(https://projects.theforeman.org/projects/foreman/wiki/Translating)
* Prepend `[WIP]` for work in progress to prevent bots from triggering actions
* Be patient, we will do our best to take a look as soon as we can
* Explain the purpose of the PR, attach screenshots if applicable
* Be nice and respectful
We are running bots that will poke you if you miss an item from the list :-)
--->
theforeman:1.18-stable
← tbrisker:23961-118
opened 11:20AM - 06 Aug 18 UTC
<!---
Thank you for contributing to The Foreman, please read the
[following … guide](https://www.theforeman.org/contribute.html), in short:
* [Create an issue](https://projects.theforeman.org/projects/foreman/issues)
* Reference the issue via `Fixes #1234` in the commit message
* Prefer present-tense, imperative-style commit messages
* Mark all strings for translation, see [Translating section in the guide]
(https://projects.theforeman.org/projects/foreman/wiki/Translating)
* Prepend `[WIP]` for work in progress to prevent bots from triggering actions
* Be patient, we will do our best to take a look as soon as we can
* Explain the purpose of the PR, attach screenshots if applicable
* Be nice and respectful
We are running bots that will poke you if you miss an item from the list :-)
--->
ekohl
August 6, 2018, 12:07pm
10
Per the discussion on it was also built into 1.17 and 1.18 because it was assumed to be compatible.
theforeman:rpm/develop
← chris1984:update-vsphere
opened 07:55PM - 09 Jul 18 UTC
For plugin updates, please indicate which repos this should be built into:
* … [x] Nightly
* [ ] 1.18
* [ ] 1.17
* [ ] 1.16
See Foreman's [plugin maintainer documentation](https://projects.theforeman.org/projects/foreman/wiki/How_to_Create_a_Plugin#Release-strategies) for more information.
---
We should probably not have open ended dependencies and this should have been a 3.0 if the API breakage was intentional. If it was unintentional then perhaps a 2.3.1 could be released to restore compatibility.