# Error upgrade VMWare tools

**URL:** <https://forum.ansible.com/t/error-upgrade-vmware-tools/10684>\
**Category:** Get Help\
**Tags:** vmware\
**Created:** [November 4, 2024, 2:59pm UTC](https://forum.ansible.com/t/error-upgrade-vmware-tools/10684 "2024-11-04T14:59:26Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![ansibliano](https://avatars.discourse-cdn.com/v4/letter/a/eb9ed0/32.png) [@ansibliano](https://forum.ansible.com/u/ansibliano)\
**Post date:** [November 4, 2024, 2:59pm UTC](https://forum.ansible.com/t/error-upgrade-vmware-tools/10684/1 "2024-11-04T14:59:26Z")

</div>

Hi,  
I am trying to upgrade VMWare tools using the module: community.vmware.vmware\_guest\_tools\_upgrade

I obtain: “msg”: “VMware tools could not be upgraded”

this is the part of ansible yml:

```auto
    - name: Upgrade VMware Tools using uuid
      community.vmware.vmware_guest_tools_upgrade:
        hostname: "{{ vcenter_hostname }}"
        username: "{{ vcenter_username }}"
        password: "{{ vcenter_password }}"
        datacenter: "{{ vcenter_datacenter }}"
        force_upgrade: true
        uuid: "{{ vm_info.instance.hw_product_uuid }}"
      delegate_to: localhost

```

It isn’t about uuid problem, but I don’t know how to solve.  
My collection is “community.vmware” version “5.1.0”

My vcenter version: 8.0.3

How could I investigate on it?

Thanks  
Mario

---

<div class="post-metadata">

**Author:** ![mariolenz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mariolenz/32/108_2.png) [@mariolenz](https://forum.ansible.com/u/mariolenz)\
**Post date:** [November 4, 2024, 5:04pm UTC](https://forum.ansible.com/t/error-upgrade-vmware-tools/10684/2 "2024-11-04T17:04:00Z")

</div>

What are the version and running status of VMware Tools?

You should get them from vCenter or with the `community.vmware.vmware_guest_tools_info` module.

---

<div class="post-metadata">

**Author:** ![ansibliano](https://avatars.discourse-cdn.com/v4/letter/a/eb9ed0/32.png) [@ansibliano](https://forum.ansible.com/u/ansibliano)\
**Post date:** [November 5, 2024, 8:31am UTC](https://forum.ansible.com/t/error-upgrade-vmware-tools/10684/3 "2024-11-05T08:31:22Z")

</div>

Thank you Mario.

From the vcenter I read the VMWare Tools status: Running, version:12325 (Upgrade available)  
Mario

The problem seems to be about collections.  
I customized my restricted collections with:

```auto
Collection Version
------------------ -------
ansible.utils 5.1.2
ansible.windows 2.5.0
cloud.common 4.0.0
community.general 9.5.0
community.vmware 5.1.0
community.windows 2.3.0
vmware.vmware 1.6.0
vmware.vmware_rest 4.2.0

```

and I have the problem mentioned.

If I restore the default old collections, it works:

```auto
Collection Version
---------------------------------------- -------
amazon.aws 8.2.1
ansible.netcommon 6.1.3
ansible.posix 1.5.4
ansible.utils 4.1.0
ansible.windows 2.5.0
arista.eos 9.0.0
awx.awx 24.6.1
azure.azcollection 2.7.0
check_point.mgmt 5.2.3
chocolatey.chocolatey 1.5.3
cisco.aci 2.10.1
cisco.asa 5.0.1
cisco.dnac 6.20.0
cisco.intersight 2.0.20
cisco.ios 8.0.0
cisco.iosxr 9.0.0
cisco.ise 2.9.3
cisco.meraki 2.18.2
cisco.mso 2.9.0
cisco.nxos 8.1.0
cisco.ucs 1.14.0
cloud.common 3.0.0
cloudscale_ch.cloud 2.4.0
community.aws 8.0.0
community.ciscosmb 1.0.9
community.crypto 2.22.1
community.digitalocean 1.27.0
community.dns 3.0.5
community.docker 3.13.0
community.general 9.5.0
community.grafana 1.9.1
community.hashi_vault 6.2.0
community.hrobot 2.0.2
community.library_inventory_filtering_v1 1.0.1
community.libvirt 1.3.0
community.mongodb 1.7.7
community.mysql 3.10.3
community.network 5.0.3
community.okd 3.0.1
community.postgresql 3.6.1
community.proxysql 1.6.0
community.rabbitmq 1.3.0
community.routeros 2.19.0
community.sap_libs 1.4.2
community.sops 1.9.1
community.vmware 4.7.1
community.windows 2.3.0
community.zabbix 2.5.1
containers.podman 1.16.1
cyberark.conjur 1.3.0
cyberark.pas 1.0.27
dellemc.enterprise_sonic 2.5.1
dellemc.openmanage 9.7.0
dellemc.powerflex 2.5.0
dellemc.unity 2.0.0
f5networks.f5_modules 1.31.0
fortinet.fortimanager 2.7.0
fortinet.fortios 2.3.7
frr.frr 2.0.2
google.cloud 1.4.1
grafana.grafana 5.5.1
hetzner.hcloud 3.1.1
ibm.qradar 3.0.0
ibm.spectrum_virtualize 2.0.0
ibm.storage_virtualize 2.5.0
ieisystem.inmanage 2.0.0
infinidat.infinibox 1.4.5
infoblox.nios_modules 1.7.0
inspur.ispim 2.2.3
inspur.sm 2.3.0
junipernetworks.junos 8.0.0
kaytus.ksmanage 1.2.2
kubernetes.core 3.2.0
kubevirt.core 1.5.0
lowlydba.sqlserver 2.3.4
microsoft.ad 1.7.1
netapp.cloudmanager 21.22.1
netapp.ontap 22.12.0
netapp.storagegrid 21.12.0
netapp_eseries.santricity 1.4.1
netbox.netbox 3.20.0
ngine_io.cloudstack 2.5.0
ngine_io.exoscale 1.1.0
openstack.cloud 2.2.0
openvswitch.openvswitch 2.1.1
ovirt.ovirt 3.2.0
purestorage.flasharray 1.31.1
purestorage.flashblade 1.18.0
sensu.sensu_go 1.14.0
splunk.es 3.0.0
t_systems_mms.icinga_director 2.0.1
telekom_mms.icinga_director 2.1.2
theforeman.foreman 4.2.0
vmware.vmware 1.5.0
vmware.vmware_rest 3.2.0
vultr.cloud 1.13.0
vyos.vyos 4.1.0
wti.remote 1.0.10

```

I don’t think the problem is about the different community.vmware version.  
Do I need more collections to install VMWare Tools?

Thanks a lot.  
Mario

---

<div class="post-metadata">

**Author:** ![mariolenz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mariolenz/32/108_2.png) [@mariolenz](https://forum.ansible.com/u/mariolenz)\
**Post date:** [November 5, 2024, 5:25pm UTC](https://forum.ansible.com/t/error-upgrade-vmware-tools/10684/4 "2024-11-05T17:25:00Z")

</div>

> [@ansibliano](#):
>
> I don’t think the problem is about the different community.vmware version.

I think you’re wrong there and it _does_ have something to do with the different `community.vmware` version. If it works with 4.x but doesen’t with 5.x, it looks like I broke something.

I’ve opened an [issue](https://github.com/ansible-collections/community.vmware/issues/2237) about this. Since it looks like a bug in the collection, I think we should track this in the repo instead of here.

Have a look at it if you want to have more information.

---

<div class="post-metadata">

**Author:** ![mariolenz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mariolenz/32/108_2.png) [@mariolenz](https://forum.ansible.com/u/mariolenz)\
**Post date:** [November 18, 2024, 5:04pm UTC](https://forum.ansible.com/t/error-upgrade-vmware-tools/10684/5 "2024-11-18T17:04:32Z")

</div>

I’m pretty sure I’ve fixed this [here](https://github.com/ansible-collections/community.vmware/pull/2243).

I’m planning to do a new release containing this change end of November / (very) early December.

---

<div class="post-metadata">

**Author:** ![mariolenz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mariolenz/32/108_2.png) [@mariolenz](https://forum.ansible.com/u/mariolenz)\
**Post date:** [November 30, 2024, 2:46pm UTC](https://forum.ansible.com/t/error-upgrade-vmware-tools/10684/6 "2024-11-30T14:46:04Z")

</div>

I’ve released 5.2.0 today an hope your issue is fixed there.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/ansible/original/1X/1882d9a01da5d8996a862359b0913cc568a39b84.svg) [@system](https://forum.ansible.com/u/system)\
**Post date:** [December 30, 2024, 2:46pm UTC](https://forum.ansible.com/t/error-upgrade-vmware-tools/10684/7 "2024-12-30T14:46:34Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.