-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
4.19.0
-
Moderate
-
None
-
NE Sprint 264, NE Sprint 265, NI&D Sprint 266, NI&D Sprint 268, NI&D Sprint 269, NI&D Sprint 270
-
6
-
Rejected
-
False
-
Description of problem:
The error log output ("failed to create ServiceMeshControlPlane") appears in the e2e-aws-gatewayapi. It fails a few times before eventually creating the ServiceMeshControlPlane however it is expected that it should be not failing.
Version-Release number of selected component (if applicable):
How reproducible:
Always
Steps to Reproduce:
1. Look through the logs of e2e-aws-gatewayapi
2.
3.
Actual results:
ERROR operator.init controller/controller.go:263 Reconciler error {"controller": "gatewayclass_controller", "object": {"name":"openshift-default"}, "namespace": "", "name": "openshift-default", "reconcileID": "e18f9589-f527-4802-87aa-bc6ebb8240fd", "error": "failed to create ServiceMeshControlPlane openshift-ingress/openshift-gateway: Internal error occurred: failed calling webhook \"smcp.mutation.maistra.io\": failed to call webhook: Post \"https://istio-operator-service.openshift-operators.svc:443/mutate-smcp?timeout=10s\": no endpoints available for service \"istio-operator-service\"", "errorCauses": [{"error": "failed to create ServiceMeshControlPlane openshift-ingress/openshift-gateway: Internal error occurred: failed calling webhook \"smcp.mutation.maistra.io\": failed to call webhook: Post \"https://istio-operator-service.openshift-operators.svc:443/mutate-smcp?timeout=10s\": no endpoints available for service \"istio-operator-service\""}]
Expected results:
No log error in creating the ServiceMeshControlPlane
Additional info:
You can pick any arbitrary job run for a PR from https://prow.ci.openshift.org/job-history/gs/test-platform-results/pr-logs/directory/pull-ci-openshift-cluster-ingress-operator-master-e2e-aws-gatewayapi to view the log output
