Skip to main content

has anyone else seen this issue?  We have a Azure NC2 cluster (not in prd yet) and have been notified that we could face the following issue

We would like to inform you about a recently discovered issue where inconsistent CPU microcode configuration will affect the ability to live migrate VMs (internally tracked as ENG-723026). 

This arises when a Nutanix cluster is upgraded to AHV versions 20230302.103003, 20230302.102005, 10.0.0.1, or 10.0, followed by cluster expansion or node replacement. In such cases, live migration of newly created VMs will encounter issues. 

Our records show that your Nutanix Cloud Cluster is susceptible to this inconsistent CPU microcode configuration. For details on the action, you can take to remediate, please refer to this Knowledge Base Article. If you have any questions or require assistance, please feel free to open a support ticket. 
 

 

Anyway I planned on doing the  upgrade to the fixed version in the AHV 20230302 track el8.nutanix.20230302.103014 with the associated AOS 6.10.1.5 (currently we’re running 6.10.1) But I have found the following issue. I can select el8.nutanix.20230302.103014 in LCM BUT only AOS 7.0.1 is shown for AOS and not 6.10.1.5 We see the issue on both our Azure NC2 cluster and our on-prem cluster.  I opened a ticket and the SRE said it was a dependency, but I don’t think that’s correct as  el8.nutanix.20230302.103014 goes with AOS 6.10.x LTS and NOT AOS 7.x which aligns with AHV 10.x I am waiting for the SRE to get back to me as I think this is an LCM issue.  We don’t have any plans to switch to AOS 7.x and AHV 10.x until the start of next year. 

 

 

  

Be the first to reply!