Closed ashkuren closed 1 year ago
@ashkuren Do we need to have Vmware Tools installed for this feature to work?
open-vm-tools and its dependencies should be installed which is already the case. After some investigation, the symptoms are similar to this post. open-vm-tools
are not identified on the first boot, vm is not powered on and customizations fail.
After first boot/shutdown/convert to template the vm customizations are triggered but fail because of another issue with cloud-init
. I think this should be a separate issue, but in order to workaround it, i have changed this parameter:
# Enable Vmware custom spec (Disable Cloudinit vmware custom spec)
sed -i '/^disable_vmware_customization/ s/false/true/' /etc/cloud/cloud.cfg
This issue has been automatically marked as stale because it has not been updated for at least 3 months.
If you can still reproduce this issue on the current release or on master
, please reply with all of the information you have about it in order to keep the issue open.
Thank you for all your contributions! More information about the ManageIQ triage process can be found in the triage process documentation.
This issue has been automatically closed because it has not been updated for at least 3 months.
Feel free to reopen this issue if this issue is still valid.
Thank you for all your contributions! More information about the ManageIQ triage process can be found in the triage process documentation.
As stated, by default OVA image is unable to use vmware customization specs. Image:
kasparov-1
VMware error:
The reason could be related to this error that shows on
dnf
command execution.