VyOS 1.5 open-vm-tools.service missing

[I-n-d-y]

Hi,

I have recently updated from VyOS 1.5-rolling-202401130024 to 1.5-rolling-202405060019 and noticed that the open-vm-tools.service seems to be missing.

VyOS 1.5-rolling-202401130024

root@vyos:~# systemctl status open-vm-tools.service
● open-vm-tools.service - Service for virtual machines hosted on VMware
     Loaded: loaded (/lib/systemd/system/open-vm-tools.service; enabled; preset: enabled)
     Active: active (running) since Sat 2024-04-20 14:53:24 CEST; 3 weeks 1 day ago
       Docs: http://open-vm-tools.sourceforge.net/about.php
   Main PID: 736 (vmtoolsd)
      Tasks: 3 (limit: 2337)
     Memory: 6.8M
        CPU: 30min 3.101s
     CGroup: /system.slice/open-vm-tools.service
             └─736 /usr/bin/vmtoolsd

VyOS 1.5-rolling-202405060019

root@vyos:~# systemctl status open-vm-tools.service
Unit open-vm-tools.service could not be found.

Is this a bug?

Thanks,

Lars

[Apachez]

Related?

https://vyos.dev/T6312

Fixed in 1.5-rolling-202405070019

Release 1.5-rolling-202405070019 · vyos/vyos-rolling-nightly-builds

So try updating your 1.5 install to above or newer and return with the result.

[I-n-d-y]

Thanks - that’s it.

I updated to VyOS 1.5-rolling-202405121403 and the open-vm-tools are working again.

root@vyos:~# systemctl status open-vm-tools
● open-vm-tools.service - Service for virtual machines hosted on VMware
     Loaded: loaded (/lib/systemd/system/open-vm-tools.service; enabled; preset: enabled)
     Active: active (running) since Tue 2024-05-14 07:43:57 CEST; 1min 5s ago
       Docs: http://open-vm-tools.sourceforge.net/about.php
   Main PID: 639 (vmtoolsd)
      Tasks: 3 (limit: 2337)
     Memory: 9.6M
        CPU: 318ms
     CGroup: /system.slice/open-vm-tools.service
             └─639 /usr/bin/vmtoolsd

May 14 07:43:57 localhost.localdomain systemd[1]: Started open-vm-tools.service - Service for virtual machines hosted on VMware.

I also posted a note on ⚓ T6312 open-vm-tools missing in nightly-builds starting from version 1.5-rolling-202404220020 that it’s working again.