URL:
Reporter RHNID:
Section: -
Language: en-US (English)
Workaround: By the time you get back the prompt, you should be able to deploy control plane manually. Either do so from the OpenShift web console, or deploy the /home/student/DO328/solutions/install-mesh/ossm-install.yml and /home/student/DO328/solutions/install-mesh/ossm-smmr.yml (name default, project istio-system).

Description: When executing lab install-mesh solve, we deploy all operators by using YAML manifests and wait until all operators are installed in the Service Mesh project.

Despite the status of all operators in the istio-system project is Succeeded, deploying control plane may fail because the operator is not yet ready to serve the OSSM APIs.

When this happens, the Deploying Control Plane step fails (and all subsequent steps too). In the logs (/var/tmp/labs), you can see Control plane deployment timed out.

The actual error is:

Error from server (InternalError): error when creating "/home/student/DO328/solutions/install-mesh/ossm-install.yml": Internal error occurred: failed calling webhook "smcp.mutation.maistra.io": Post "https://maistra-admission-controller.openshift-operators.svc:443/mutate-smcp?timeout=10s": dial tcp 10.10.0.44:11999: connect: connection refused

To work around the issue, we have added a sleep timer in the solve function, and multiple tries. However, the proper fix would be to find a way to wait until the operators are fully ready to serve the APIs.

Possibly unrelated KCS: https://access.redhat.com/solutions/5313251