From time to time we have to run the Nutanix crashcart /usr/local/bin/network-crashcart to configure the AHV+CVM network IPs.
This command has some guard rails in place to stop it working when the host is already in a cluster (very sensible!) but sometimes those guard rails are a little too tight and it doesn’t work even when the cluster is not in a cluster.
I observed this recently building a couple of new clusters on hardware that had been powered on but not configured for 3 weeks, the behaviour was consistent across all 28 nodes being built and fortunately was cleared after a reboot and waiting a few minutes for the CVM to boot up.
No idea why, next time it happens I’ll dig a little more and look at what logic isn’t being matched leading to the message being displayed to find a less nuclear option than a reboot.