-
Bug
-
Resolution: Not a Bug
-
Major
-
None
-
4.13.z
-
No
-
False
-
Description of problem:
New provisioned nodes receive an incorrect taint value. oc get nodepools -n ocm-production-<snip> -o yaml | grep taint -A 5 taints: - effect: NoSchedule key: test.com/dedicated value: multitenant oc get nodes <snip>.ec2.internal -o yaml | grep -i taints -A 5 taints: - effect: NoSchedule key: test.com/dedicated value: <random hash>
Version-Release number of selected component (if applicable):
HCP: 4.13.13 HyperShift Operator: version":"openshift/hypershift: 51dcea7b42a315af3079b63b527040f27b052c98. Latest supported OCP: 4.13.0"
How reproducible:
Seen on multiple clusters and multiple nodes
Steps to Reproduce:
1. 2. 3.
Actual results:
Node taint value is set to some hash value instead of "multitenant"
Expected results:
Node taint value is properly propagated as "multitenant"
Additional info:
Must gather and details in the comments.