Found the same problem here, after a 9.5 upgrade.
Two of my 3 VM proxies had replicas, so my jobs, when managed through these two proxies, were falling back to network mode since 9.5.
Case is #01991700, Il'ya was a VERY helpful and skilled engineer to detect this problem on 1st December.
Just after deleting my two proxies replicas, jobs started to work in hot-add mode again
Happy to read that there will be a patch!
BTW, here is a way to find if you have duplicate UUIDs:
- getting Bios UUID Inside a VM (PowerShell): (Get-WmiObject Win32_ComputerSystemProduct).UUID, looks like : DAE32E42-2750-3619-C366-B871E3EB9EF5
- getting UUID VM in vSphere/ESXi: download/open the .vmx file, search for Something like uuid.bios = "42 2e e3 da 50 27 19 36-c3 66 b8 71 e3 eb 9e f5"
These two information are to confirm you have the right information about the right VM.
Note that some bytes are reversed, DAE32E42 is the same as "42 2e e3 da", same for the next 4 bytes
Now, to check your vCenter database, go to https://myvcenterserver
/mob, login and go to query ServiceContent/SearchIndex/FindAllByUUID.
The search UUID string have to be written precisely in that manner: 8symbols+dash+4symbols+dash+4symbols+dash+4symbols+dash+all_the_rest.
That search immediately show me that I had duplicated ID on my Veeam proxies VMs (even if I can see obviously my VM replicas in vCenter):
Again, many thanks to Il'ya (Veeam support) for his outstanding mastering