Resolving IVIA runtime configuration failures

Edit online

The IVIA deployment can fail during runtime configuration when the setup job returns an invalid status code response. In most cases, the failure is caused by an intermittent timing or readiness issue during deployment.

Symptoms

The IVIA deployment shows one or more of the following symptoms:
  • The IVIA runtime configuration step fails with an invalid status code error message.
  • The ivia-apps-setup-job job or related pods show an Error status in the Red Hat OpenShift console.
  • The IVIA application in Argo CD remains out of sync or shows a failed synchronization state.
  • Manually deleting the failed job and synchronizing the application does not always resolve the failure.

Cause

This problem is typically caused by an intermittent timing or readiness issue during IVIA deployment. Some IVIA resources start before dependent services are fully ready, which causes the runtime configuration job to fail and return an invalid status code. If the initial failure leaves partial resources, volumes, or unfinished installation state in the namespace, subsequent synchronization attempts can continue to fail until the environment is cleaned up and redeployed.

Solution

Use one of the following recovery options:
Option 1: Targeted recovery

In most cases, deleting the failed job or pod and then resynchronizing the failing IVIA application resolves the problem.

  1. Open the project that contains the IVIA deployment in the Red Hat OpenShift console.
  2. Locate and delete the failed ivia-apps-setup-job job or its failed pod.
  3. Open the Argo CD instance and resynchronize the failing IVIA application.

The application resynchronizes and the deployment usually completes after the transient readiness issue clears.

Option 2: Full cleanup and redeploy

If targeted recovery does not resolve the issue, perform a full cleanup and redeployment. For detailed steps, see Resolving IVIA deployment failures with partial or stale state.