Troubleshooting and Messages

Use the following information to troubleshoot issues that are reported in messages.

Pre-Installation Messages

The following messages are issued before installation or upgrade of the Helm chart, if requirements are not met. If you receive any of these messages, the installation or upgrade is aborted, and you must resolve the issues and then retry to install or upgrade.

Install|Upgrade "<release-name>" failed: pre-install|pre-upgrade hooks failed: 1 error occurred: * job <release-name>-checkreq-helm-img failed: PodFailurePolicy

Explanation: Verification of whether the Agent image version matches the Helm chart version ended in status failed. Installation or upgrade is aborted.

Corrective Action: Do the following:

1. Check the job's pod logs for specific validation failures, using the following command:
   kubectl logs -n <namespace> <release-name>-checkreq-helm-img
   Look for the following message:

   Validation failed: Control-M for Kubernetes Image version (<IMAGE_VERSION>) does not match the Helm chart version (<CHART_VERSION>). Align the versions to proceed with installation or upgrade.

2. Ensure that the Agent image version matches the Helm chart version, and try again.

Install|Upgrade "<release-name>" failed: pre-install|pre-upgrade hooks failed: 1 error occurred: * job <release-name>-checkreq-aapi-min-ver failed: PodFailurePolicy

Explanation: Verification of the Control-M Automation API version ended in status failed. Installation or upgrade is aborted.

Corrective Action: Do the following:

1. Check the job's pod logs for specific validation failures, using the following command:
   kubectl logs -n <namespace> <release-name>-checkreq-aapi-min-ver

2. In the job pod log, look for any of the following messages and perform the necessary corrective actions:

   Failed to fetch Control-M Automation API version file from <AAPI_ENDPOINT>

   Explanation: The version file could not be retrieved from the specified Control-M Automation API endpoint.

   Corrective Action: Verify that the API endpoint that you specified (through the input Helm parameter) is correct and accessible from the Kubernetes environment where the job runs.

   FAIL: Control-M Automation API version <AAPI_VERSION> is below the required minimum <AAPI_MIN_VERSION>. Please upgrade to meet or exceed this version.

   Explanation: The detected Control-M Automation API version is lower than the minimum required version.

   Corrective Action: Upgrade Control-M Automation API to a version that meets or exceeds the required minimum version, as listed in Control-M-for-Kubernetes-Compatibility.