@Eric-The_Viking
More likely this is a defect, would appreciate if you could open a case with Nutanix support to check this out since this needs more investigation and following some KBs
Hi Eric,
This is most likely a false-positive alert from your NCC version, we are aware of this issue and have seen it in NCC-3.8.0 & NCC-3.9.4, the fix was implemented in NCC-3.10.1.
You can verify that it’s false positive simply by seeing the same name in the CVM shell or in Prism as it was previously.
However, it’s recommended that you open a case with Nutanix to verify this.
Hi Eric,
This is most likely a false-positive alert from your NCC version, we are aware of this issue and have seen it in NCC-3.8.0 & NCC-3.9.4, the fix was implemented in NCC-3.10.1.
You can verify that it’s false positive simply by seeing the same name in the CVM shell or in Prism as it was previously.
However, it’s recommended that you open a case with Nutanix to verify this.
Thank you mate, I have the same issue in a cluster. I hope that NCC-3.10.1 will be released soon ;)
I’m glad I could help!
I’m not aware of an exact date but I’m sure it won’t take long for the NCC-3.10.1 to be released
There is a plan to include a tool to rename CVMs, this plan is included in the following ENG ticket:
Engineering ENG-152544
Need a utility to change CVM display name in prism for AHV cluster
Team has already verified the fix in 5.16 and 5.11.3 - not sure how 5.10.9 got released.
Regs.
Antonio