I have one host in a 6 server farm that won't scan... In the esxupdate log, the last entry is:
DEBUG: vibcache: Loading repomd/apt metadata
top shows esxupdate cpu usage at 99%
Scan task eventually times out in vCenter. vCenter and VUM are 4.1.0
VUM logs show the scan starting then the task failing some time later
I'm fairly confident its not a VUM issue as this server can patch the other hosts (same subnet, all in the same fw rule group)
Any thoughts please?