You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 1, 2021. It is now read-only.
The following hash get's passed from foreman, through fog-vsphere, but never makes it to the customization. (at least, it doesn't execute the commands, and no evidence of them is found in any of the run once parts in windows.
So we meet again. 😄 I'm going to do a quick glance at all the PRs and issues and handle all the simple stuff now. I assure you I'll come back to this as soon as I've done a first pass.
@finkelamein Sorry it took so long to get back to you. Is this still an issue? If so, I can take a look again. Just let me know whether I should close this or investigate. Thanks!
Hi, I'd guess it's still an issue, but I switched jobs since then, and I
can't test this anymore for lack of both foreman and VMware farm.
Feel free to do with this as you want
@finkelamein Sorry it took so long to get back to you. Is this still an issue? If so, I can take a look again. Just let me know whether I should close this or investigate. Thanks!
This is still an issue. I have just setup a fresh vCenter and Foreman. Trying to accomplish automatic provisioning of Windows VMs with Puppet agent. However, the commands are not ran anytime.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Coming from a problem noticed in foreman vpshere integration, through fog-vsphere, ending over here.
See:
fog/fog-vsphere#37 (comment)
http://projects.theforeman.org/issues/14979
The following hash get's passed from foreman, through fog-vsphere, but never makes it to the customization. (at least, it doesn't execute the commands, and no evidence of them is found in any of the run once parts in windows.
hash that get's passed to rbvmomi
Any idea what's going on?
The text was updated successfully, but these errors were encountered: