Worker node duplicated itself

[Amarokada]

We're running on 12.3 currently with all the correct AHV plugins and appliance versions, against AOS 7. This is working fine for the most part, but we noticed that one of our workers has somehow duplicated itself in Nutanix. The name and IPs are the same for both VMs, and one stays on 100% of the time. It hasn't caused our backups to fail, even though we see this particular worker used in some of the jobs.

So this is more of a warning that there must be some kind of bug somewhere that causes this. I've disabled this worker for now and will power down the duplicate. Shall I keep both of them if Veeam want to check our environment to track down this bug? Since we have the automatic updating of workers turned off, I'm wonder how this can possibly have happened. Does Veeam attempt to push out a worker if for some reason it doesn't get feedback from an existing one?

Rob

[Amarokada]

Since 7.1 is released I'll be updating on Monday, since we've had the scheduling bug twice in the past and apparently this is fixed.

[ronnmartin61]

Yes the scheduler issue fix is in 7.1. Feel free to delete the duplicate worker. Any worker can be deleted at any time (except if it's actively processing backup/restore operations of course) and will simply be re-deployed when it's needed.