Troubleshooting

This page is a work in progress.

AWS

No known issues yet.

Azure

No known issues yet.

Google Cloud

No known issues yet.

IBM Cloud

ImagePullError

If you see errors pulling images from the repository this tends to mean the registry is in a different zone. By default, registries are open to nodes inside the same zone. If they are different, you can add a token like this:

ibmcloud cr token-add --description "Registry token" --non-expiring --readwrite
kubectl --namespace diffblue create secret docker-registry registry-token --docker-server=registry.eu-de.bluemix.net --docker-username=token --docker-password=<token from first step> --docker-email=a@b.com

Ensure that the token is replaced as well as the correct registry server. Then add these lines to the spec sections of the deeptest-worker, keymaker, and front-end deployment YAMLs and the application-server stateful set YAML:

spec:
imagePullSecrets:
- name: registry-token

Then reapply these YAMLs.

Mongo CrashLoopBackoff

In some cases Mongo can fail to start in the initial interval timeframe set in the manifest YAML files. This seems to be an issue with IBM Cloud only, and how volumes take some time to start. The solution is to increase the initialDelaySeconds: 30 value to around 100 seconds in both the liveness and readiness checks.

results matching ""

    No results matching ""