-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
4.17, 4.18
-
Critical
-
None
-
Proposed
-
False
-
Description of problem:
aws-ebs-csi-driver-controller-xxxx pod missing tolerations specified in hypershift create clusteraws --tolerations
Version-Release number of selected component (if applicable):
4.17, 4.18
How reproducible:
100%
Steps to Reproduce:
1. oc adm taint node xxxx(all nodes) taint-test=Exists:NoSchedule 2. hcp create cluster aws with--toleration=key=taint-test,operator=Exists,effect=NoSchedule 3. check CP pods
Actual results:
➜ oc get node --no-headers | while read -r name _ _ _; do oc adm taint node "$name" taint-test=Exists:NoSchedule; done ➜ hcp create cluster aws --role-arn arn:aws:iam::460538899914:role/9a09fa799704983c5a48 --sts-creds /tmp/secret/sts-creds.json --toleration=key=taint-test,operator=Exists,effect=NoSchedule --name 9a09fa799704983c5a48 --infra-id 9a09fa799704983c5a48 --node-pool-replicas 3 --instance-type m5.xlarge --base-domain origin-ci-int-aws.dev.rhcloud.com --region us-east-1 --pull-secret /etc/ci-pull-credentials/.dockerconfigjson ➜ oc get pod -n local-cluster-9a09fa799704983c5a48 | grep -v "Running" NAME READY STATUS RESTARTS AGE aws-ebs-csi-driver-controller-bb96c5fdd-4qk2l 0/12 Pending 0 16m
Expected results:
aws-ebs-csi-driver-controller-xxxx can be Running
Additional info:
- relates to
-
OCPSTRAT-1391 [Tech Preview] HCP Control Plane Tolerations
- Closed