-
Bug
-
Resolution: Not a Bug
-
Undefined
-
None
-
4.11
-
None
-
Low
-
None
-
False
-
Description of problem:
wrong error message about violating the master node quorum
Version-Release number of selected component (if applicable):
Cluster version is 4.11.0-0.nightly-2023-01-11-025441
How reproducible:
100%
Steps to Reproduce:
Violate master quorum: 1. Install Node maintenance operator 2. Start maintenance for first master oc create -f - << EOF apiVersion: nodemaintenance.medik8s.io/v1beta1 kind: NodeMaintenance metadata: name: master-0-0 spec: nodeName: master-0-0 EOF 3. Wait until maintenance succeeded oc get nm master-0-0 -o json -w | jq '.status.phase' 4. Verify that can't start maintenance for second master oc create -f - << EOF apiVersion: nodemaintenance.medik8s.io/v1beta1 kind: NodeMaintenance metadata: name: master-0-2 spec: nodeName: master-0-2 EOF
Actual results:
Error from server (can not put master/control-plane node into maintenance at this moment, it would violate the master/control-plane node quorum): error when creating "STDIN": admission webhook "vnodemaintenance.kb.io" denied the request: can not put master/control-plane node into maintenance at this moment, it would violate the master/control-plane node quorum
Expected results:
Error from server (can not put master node into maintenance at this moment, it would violate the master node quorum): error when creating "STDIN": admission webhook "vnodemaintenance.kb.io" denied the request: can not put master node into maintenance at this moment, it would violate the master node quorum
Additional info:
Actual result is message for 4.12 clusterversion