mbx64

+1 There should be no requirement for datacenter. But: Throw an error, if you find more than one VM, which might happen if you look fo a VM via display...

This: ```yaml community.vmware.vmware_content_library_items: - content_library: "abc123" - item: "my_awesome_template.ova" - state: present - file: "my_local_file.ova" ``` should probably look like this: ```yaml community.vmware.vmware_content_library_item: content_library: "abc123" name: "my_awesome_template.ova" state: present file:...

@balnbibarbi Yes, it looks OK to me.

As a workaround (until fixed) you can add `esxi_hostname: foobar`, literally, as the name will be ignored when connecting to ESXi: ```yaml - name: Add Management Network VM Portgroup community.vmware.vmware_portgroup:...

I do not think this is an issue of `vmware_deploy_ovf`. It was a problem with some VCSA images.

Instead of: ```yaml url: "https://supersecure.url/path/to/file.ovf" username: abc password: 123 ``` I recommend something like: ```yaml url: https://supersecure.url/path/to/file.ovf url_username: abc url_password: 123 url_validate_certs: true ``` This is similar to what [ansible.builtin.get_url](https://docs.ansible.com/ansible/latest/collections/ansible/builtin/get_url_module.html#parameter-url_password)...

@yurnov Yes, that's almost what I am currently doing. You also have to add the `KUBECTL_VSPHERE_PASSWORD` environment variable to your first play. Your second play is not needed. You can...

@vrhinow This is the same fix that has been already merged into this repo: https://github.com/haproxytech/vmware-haproxy/pull/34 @akutz Can you publish a new release of the current state of this repo? Your...

In this case I would recommend to format the Ventoy partition with FAT and the 3rd partition with exFAT. Put your large ISO on the 3rd partition and "VentoyVlnk" it...