Troubleshooting the deployment

Failed Upgrade #1

It might happen that the helm installation or upgrade fails with the following error:

Error: UPGRADE FAILED: another operation (install/upgrade/rollback) is in progress

This error occurs when a previously triggered upgrade of the deployment is still in progress. This can be the case if a pipeline is run multiple times within a short period of time or if the previous deployment attempt was not / only partially successful.

The issue can be resolved by resetting the helm release to a previous state. Use the following helm commands:

# get your release name
helm ls -a

# get the history of past releases and look up the last working version
helm history <releasename>

# roll back to the last working release
helm rollback <releasename> <releasenumber>

Failed Upgrade #2

You might experience the following error message:

Error: UPGRADE FAILED: timed out waiting for the condition

Verify the configuration of the deployed cadenza. Check the Kubernetes logs for any hints on why cadenza didn’t start up.

Failed Startup

A common error is that the Cadenza Database Migration Tool wasn’t deployed or executed. See How to use the Database Migration Tool.