Open PrymalInstynct opened 1 year ago
were you able to resolve this issue? I encountered this exact issue and was curious if you found a resolution. If not, my next step would be to rewrite the playbook to use the CLI instead of the OVF.
I was having the same issue when deploying VCSA 8 to ESXi and was able to get it working by adding these two lines to the properties
parameter in the vmware_deploy_ovf
task:
guestinfo.cis.upgrade.import.directory.userConfigurable: 'True'
guestinfo.cis.upgrade.import.directory: '/storage/seat/cis-export-folder'
I found the solution from this article. Says for workstation and fusion, but it fixed the issue for me on ESXi too.
SUMMARY
When attempting to deploy the VCSA OVA (Version 7.0U3k) with ansible the tasks are successful but the resulting Virtual Machine fails upon First Boot.
I am opening this issue against the ansible community,vmware collection because this behavior does not occur when using the VCSA OVA (Version 7.0U3d).
It also does not occur when installing the VCSA OVA (Version 7.0U3k) with the
vcsa-cli-installer
application built into the VCSA ISOISSUE TYPE
COMPONENT NAME
community.vmware.vmware_deploy_ovf
ANSIBLE VERSION
COLLECTION VERSION
CONFIGURATION
OS / ENVIRONMENT
I have attempted to run the same playbook from Red Hat 8.7, Fedora 36, Fedora 37, and Arch Linux
STEPS TO REPRODUCE
playbook.yml
vcsa_vars.yml
EXPECTED RESULTS
I expect the OVA to be deployed, configured, and be ready for use
ACTUAL RESULTS
The Ansible Tasks complete however the VCSA VM produces an error upon the completion of the First Boot setup tasks
fbInstall.json
From /var/log/firstboot/ on the VCSA Host