Windows Server 2022 cluster can't update nodeweight if it configured manual failover without witness.
Please note : This is Manual failover only. This specific case don't care Quorum since 2 multisubnet. Only one site is preferred.
However, failover not possible unless Force Quorum. Failover itself work. However, when the secondary site down, entire cluster down since the nodeweight not updatable and current vote doesn't move.
Same approch is working on Windows Cluster 2019 and lower version.
Produce version : Windows Server 2022 Standard
Version : 21H2
OS Build : 20348.1970
<Reproduce issue>
2 Node - multisubnet (1 node per subnet)
Node1 - Primary
Node2 - Secondary
No witness(Node Majority)
DynamicQuorum = 1
- Node1 set as nodeweight =1, Current vote =1
- Node2 set as nodeweight =0, Current vote =0
Start Failover>
Service moved to Node2 as Primary.
After that, update nodeweight as below.
Node2 set as nodeweight =1
Node1 set as nodeweight =0 -> this is failing with following message "because changing the node weight would violate the minimum cluster quorum requirements"
It works in lowerversion of Windows cluster. Current Vote is updating to corresponding node when AssignedVote(nodeweight) is updated.
Because of this failure in Windows Server 2022, it can't failover other node and maintenance isn't possible since Node2 can't goes down since it occupied current vote as 1. it's not updatable.
Please check that ASAP.