Affects Version/s: None
Fix Version/s: None
Running puppet apply from a crontab on the puppet master to create new nodes on Vsphere VCENTER using the puppetlabs/vsphere module version 1.3.1.
Template:MODULES Bug Template customfield_10700 319564
Method Found:Needs Assessment
QA Risk Assessment:Needs Assessment
Puppet Version: 2018.1.2
OS Name/Version: Linux 6.7
Describe your issue in as much detail as possible...
Desired Behavior: command specified by the create_command parameter is running on VMs created from a generalised (syspreped) template**
Actual Behavior: command specified by the create_command parameter is *not r*unning on VMs created from a generalised (syspreped) template**
Please take a moment and attach any relevant log output and/or manifests. This will help us immensely when troubleshooting the issue.
Turning on debugging for puppet apply reveals that after 4 or 5 attempts a connection is established but then terminates with a credentials fault. Commenting out the following lines in lib/puppet/provider/vsphere_vm/rbvmomi.rb allows more attempts to be made ...
raise Puppet::Error, 'Incorrect credentials for the guest machine'
This typically works but takes 9+ attempts so we also increased the max retries from 10 to 25 ...
with_retries(:max_tries => 25,
Add module parameters to enable faults to be selectively disabled. Also add a parameter to enable max_retries to be overridden. In all cases, default behaviour can be unchanged.