Found different OS build number between cluster nodes

Question

Just want to upgrade the existing cluster 2411.3.2 to 10.2503.0.13. After a few fail and retry, now the system show the following error :

Type 'UpdateOsBuildNumberInEce' of Role 'OsUpdate' raised an exception: Found different OS build number between cluster nodes: xx 03 is running on 10.0.25398.1486, xx01 is running on 10.0.25398.1551. Command Arguments ------- --------- Update-OsBuildNumberInEce {Parameters=CloudEngine.Configurations.EceInterfaceParameters} {} <ScriptBlock> {CloudEngine.Configurations.EceInterfaceParameters, OsUpdate, UpdateOsBuildNumberInEce, C... Invoke-EceInterfaceInternal

Anyone got idea how to align with it ?

Answer 1

Hi Ken,

The error you're encountering suggests there's a mismatch in OS build versions across your cluster nodes, specifically with one node running 10.0.25398.1486 and another on 10.0.25398.1551. This inconsistency is preventing your upgrade from 2411.3.2 to 10.2503.0.13 from completing successfully.

To resolve this, you'll first need to verify the exact OS versions on each node. You can do this by checking the system properties or running a PowerShell command like [System.Environment]::OSVersion on each machine. Once confirmed, you'll need to bring all nodes to the same build level. The safest approach would be to update the node with the lower build number (10.0.25398.1486) to match the higher one (10.0.25398.1551).

If you're working with an Azure Stack HCI cluster, you might want to use the cluster-aware updating feature or PowerShell cmdlets like Update-ClusterNode to synchronize the versions. Make sure to pause any cluster operations during this update process. After all nodes are on the same build, attempt the upgrade again.

If you continue facing issues, you may need to consider temporarily removing the out-of-sync node from the cluster, updating it separately, and then rejoining it. Keep in mind that you should always ensure you have good backups and a maintenance window for such operations. The cluster health should be verified using tools like Test-Cluster before and after the upgrade process.

Let me know if you need more specific guidance based on your cluster configuration or if you encounter any other errors during this process.

Best regards,
Alex
P.S. If my answer help to you, please Accept my answer
PPS That is my Answer and not a Comment
http://ctrlaltdel.blog/