App is stuck 'Deploying...' or in an Error state

Check containers if the app does not complete its deployment.

You might have a container problem if you see the following error message.
App is stuck 'Deploying...'
Check that the container for the app was successfully deployed and is running.
sudo kubectl get pods -A -l apps.isc.ibm.com/app-type=app -L app.kubernetes.io/instance
If the container is not running or in error, use the kubectl describe command to try to diagnose the issue. 
sudo kubectl describe pod/<container_name> -n <namespace>

Verify that the Edge Gateway is accessing the correct repository. Look at the "Image:" entry under "Containers". It is the fully qualified image name and can help determine whether the images are being pulled from the wrong place. Events at the end also reveal information.

If the App pods are running, check the Edge Gateway logic containers. You can access the log information.
sudo kubectl logs deployments/deployment-synchronizer –n <namespace> &&
sudo kubectl logs deployments/deployment-operator –n <namespace>
If the Edge Gateway container logs indicate a connection issue, then it might be one of the following problems.
  • Proxy issue. Follow the instructions in Configure proxy authentication, starting at step 4.
  • DNS issue. Containers that are started in k3s do not inherit the network aliases from /etc/hosts on the Edge Gateway system. DNS can be configured by using the manageAppHost dns command. See Creating an Edge Gateway for details.
  • Certificate changed. Use the manageAppHost certificate command to download again the SOAR server certificate.

Check the locally hosted or private repository to show the available images. Verify that the app is in the repository. The app image name is the same name that is listed next to Executables in the Install App Wizard.