Troubleshooting Gremlin on OpenShift
Gremlin network timeouts
This issue is most often seen with timeout errors in both Chao and Gremlin logs.
This usually stems from network rules preventing Gremlin's access to the internet. It's important to figure out what the intended network behavior should be for Gremlin on your infrastructure with some questions:
- What other services connect to the internet within your cluster?
- Do services within your cluster rely on an HTTP proxy when connecting to the internet?
OpenShift Egress network policies
If you've reviewed the proxy requirements and determined that Gremlin does not need an HTTP proxy, but you are still unable to connect Gremlin to the internet, it's likely one or more OpenShift projects are preventing internet access with an EgressNetworkPolicy.
You can list such policies in any project with the following
If you look at the details of such a policy, you can see if network access for api.gremlin.com is denied. Here's an example of a policy which denies api.gremlin.com, because it only allows specific IP address ranges and host names while denying everything else.
Adding <span class="code-class-custom">api.gremlin.com</span> to such a <span class="code-class-custom">EgressNetworkPolicy</span> will fix this problem.
Gremlin experiments cannot find target container (OpenShift 4.9)
This issue will generate a variation of the following error:
See the Openshift 4.9 | Container does not exist article in the Gremlin knowledge base for a workaround.