10 Troubleshooting STAP Deployment

Learn about errors you may run into when deploying Oracle Communications Solution Test Automation Platform (STAP) and how to fix them.

Topics in this document:

PVC Stuck in Pending Status

If your PersistentVolumeClaims (PVC) is stuck in Pending status, follow these steps:
  • Ensure a suitable PersistentVolume (PV) is available.
  • Verify that the PV mentions a valid StorageClass and matches the available PVs.
  • Check if the storage provisioner is running and configured properly.

Note:

To check PVC status, run kubectl get pvc.

Error Message: WebSocket Not Connected

After deployment, if you get the "WebSocket Not Connected" error message:

If you have network restrictions in cluster, check the configuration for the override-values.yaml for the UI Helm Chart:

  • If you are working with Basic Auth deployment, ensure the hostname for Test Execution Service (TES) microservice is localhost with valid port numbers (if accessing outside the locally tunelled cluster, and no public load balance is used).
  • If you are working with OAuth deployment, ensure the Node IPs are mentioned for TES with correct port numbers when accessing from the same network as Cluster IPs.

helmchart.tgz File Does Not Unzip

If you are unable to unzip the helmchart.tgz file using the unzip command, perform the following actions:
  • Use the tar -xvzf helmchart.tgz command to solve this error.
  • To extract the chart to a specific directory, run the following command:
    tar -xvzf helmchart.tgz -C /desired/path

Error When Applying Image Pull Secret File

If you get an error when applying the image pull secret file, follow these steps:
  • Check if the file is correctly formatted.
  • Ensure the namespace in the image pull secret file matches the one you created.
  • Run the following command to verify if the secret was applied correctly:
    kubectl describe secret <namespace-secret>.yaml -n <namespace_name>

Deployment Stuck in ContainerCreating State

If your deployment is stuck in ContainerCreating state, follow these steps:
  • Run kubectl describe pod <pod_name> -n <namespace> to check for volume mount issues or image pull failures.
  • Ensure the imagePullSecret is correctly set up and matches the secret name.
  • Verify if the required PVs and PVCs are correctly bound.

SSL Configuration Not Working

If your SSL configuration is not working, follow these steps:
  • Ensure the secret for SSL certificates is correctly created using the following command:
    kubectl create secret generic cert-secret --from-file=<ssl cert file> -n <namespace>
  • Verify if the Helm chart is correctly referencing ssl.enabled and ssl.secretName.
  • Check logs for TLS handshake errors using the following command:
    kubectl logs <pod_name> -n <namespace>

Podman Push Fails

If your Podman push command fails, follow these steps:
  • Check if the authentication to the container registry is configured properly.
  • Verify network connectivity and registry availability.
  • Ensure the repository name follows the correct format and exists in the registry.
  • Make sure there is enough space in the registry to host the images.

NFS Does Not Mount

If you are facing errors when mounting your Network File Storage (NFS), follow these steps:
  • Ensure the correct nfs.server and nfs.path are set in the override-values.yaml file.
  • Check for NFS errors in pod logs by running the following command:
    kubectl describe pod <pod_name> -n <namespace>
  • Verify if the NFS server is reachable from the Kubernetes cluster.

Setting Proxy for your Environment and Cluster

To set proxy for your environment and cluster, run the following command in your environment and cluster both:
kubectl set env deployment --all https_proxy=proxy http_proxy=proxy no_proxy=proxy -n namespace