ServiceMesh Operator installation stuck in ContainerCreating when AquaSec Operator installed on OpenShift 4
Issue
ServiceMesh Operator pod istio-operator
is stuck on ContainerCreating and the pod logs on the OpenShift node shows:
Dec 18 07:00:38 openshift-node.example.com crio[1457]: time="2020-12-18 07:00:38.694406333Z" level=error msg="Container creation error: time=\"2020-12-18T07:00:38Z\" level=warning msg=\"exit status 2\"\ntime=\"2020-12-18T07:00:38Z\" level=error msg=\"error running hook: exit status 255, stdout: , stderr: \"\ntime=\"2020-12-18T07:00:38Z\" level=error msg=\"container_linux.go:348: starting container process caused \\\"process_linux.go:438: container init caused \\\\\\\"process_linux.go:421: running prestart hook 0 caused \\\\\\\\\\\\\\\"error running hook: exit status 255, stdout: , stderr: \\\\\\\\\\\\\\\"\\\\\\\"\\\"\"\ncontainer_linux.go:348: starting container process caused \"process_linux.go:438: container init caused \\\"process_linux.go:421: running prestart hook 0 caused \\\\\\\"error running hook: exit status 255, stdout: , stderr: \\\\\\\"\\\"\"\n"
Environment
- Red Hat OpenShift Container Platform (OCP) 4.5
- ServiceMesh 1.1
- AquaSec
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.