-
Bug
-
Resolution: Done
-
Major
-
None
-
4.13, 4.12, 4.14
-
No
-
Rejected
-
False
-
Description of problem:
We see vingressnodefirewall.kb.io: dial tcp 172.30.168.193:443: connect: connection refused error in kube-apiserver after deleting webhooks in arm64 cluster
Jun 27 16:33:13.927: INFO: Running 'oc --kubeconfig=/tmp/kubeconfig-1066174450 get kubeapiserver/cluster -o jsonpath='{.status.conditions[?(@.type=="ValidatingAdmissionWebhookConfigurationError")]}''
Jun 27 16:33:14.215: INFO: kube-apiserver admission webhook errors as
'{"lastTransitionTime":"2023-06-27T15:14:17Z","message":"vingressnodefirewall.kb.io: dial tcp 172.30.168.193:443: connect: connection refused","reason":"WebhookServiceConnectionError","status":"True","type":"ValidatingAdmissionWebhookConfigurationError"}'
We see this issue in 4.14, 4.13 and 4.12
Version-Release number of selected component (if applicable):
4.14.0-0.nightly-arm64-2023-06-27-030155 on Azure IPI cluster
How reproducible:
Not Always
Steps to Reproduce:
1. Run https://polarion.engineering.redhat.com/polarion/#/project/OSE/workitem?id=OCP-50223 test case, apply and delete custom webhooks
2. oc --kubeconfig=/tmp/kubeconfig-1066174450 get kubeapiserver/cluster -o jsonpath='{.status.conditions[?(@.type=="ValidatingAdmissionWebhookConfigurationError")]}'
Actual results:
{"lastTransitionTime":"2023-06-27T15:14:17Z","message":"vingressnodefirewall.kb.io: dial tcp 172.30.168.193:443: connect: connection refused","reason":"WebhookServiceConnectionError","status":"True","type":"ValidatingAdmissionWebhookConfigurationError"}
Expected results:
{"lastTransitionTime":"2023-06-30T07:13:56Z","status":"False","type":"ValidatingAdmissionWebhookConfigurationError"
Additional info:
https://qe-private-deck-ci.apps.ci.l2s4.p1.openshiftapps.com/view/gs/qe-private-deck/logs/periodic-ci-openshift-openshift-tests-private-release-4.14-arm64-nightly-azure-ipi-disconnected-p1-f28-destructive/1673681413041295360
