Undefined Description:Test Purpose:
The purpose of this test is to ensure the successful installation and configuration of the Advanced Cluster Management (ACM) operator in an OpenShift environment.
Failure Message:
Error from server (InternalError): error when creating "/tmp/rhdh/.ibm/pipelines/cluster/operators/acm/multiclusterhub.yaml": Internal error occurred: failed calling webhook "multiclusterhub.validating-webhook.open-cluster-management.io": failed to call webhook: Post "https://multiclusterhub-operator-webhook.open-cluster-management.svc:443/validate-operator-open-cluster-management-io-v1-multiclusterhub?timeout=10s": no endpoints available for service "multiclusterhub-operator-webhook"
Root Cause Analysis:
The ACM operator installation failed because the multiclusterhub.validating-webhook.open-cluster-management.io webhook call failed. The error message "no endpoints available for service multiclusterhub-operator-webhook" suggests that the webhook service was created, but no corresponding pods or endpoints were available to handle the webhook requests. This could be due to the operator pod not being fully initialized, a network configuration issue, or a problem with the webhook service itself.
Actionable Recommendations:1. Check the status of the multiclusterhub-operator pod and its associated webhook service. Ensure the pod is running, ready, and that the service has endpoints associated with it. Use oc get pod -n open-cluster-management and oc get svc -n open-cluster-management.
2. Review the logs of the multiclusterhub-operator pod for any errors or warnings related to the webhook service. This might provide more insight into why the endpoints are not becoming available. Use oc logs <multiclusterhub-operator-pod-name> -n open-cluster-management.
Prow Link:
https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-redhat-developer-rhdh-main-e2e-tests-osd-gcp-helm-nightly/1957019696561655808
Prerequisites (if any, like setup, operators/versions):
Steps to Reproduce
# <steps>
