Identifying the failed upgrade step in the Engineering Lifecycle Management application pod and resolving the error manually
The detailed steps to identify the failed upgrade step in the Engineering Lifecycle Management application pod and resolving the error manually to resume the upgrade process are provided.
Identifying the failed upgrade step in the Engineering Lifecycle Management application pod
- Log in to the Red Hat® OpenShift® Container Platform web console.
- Go to .
- Select the project where you installed the Engineering Lifecycle Management instance from the Project list.
- The Pods page lists the Engineering Lifecycle Management application pods and Engineering Lifecycle Management operator pod information.
- Click the pod name where the upgrade step is failed.
- Go to the Terminal tab and run the following
command.
/elm/server/getUpgradeErr.shThe script provides detailed information about the failed step, log file location, and resolve code.
Record the
Resolve codeinformation to use for resolving the error manually and resume the upgrade process.An example of the failed step information.Failed step: Merging configuration files. Logs:/elm/server/conf/jts/logs/repotools-jts_migration_jts_updateConfigurationFiles.log Resolve code: UPGRADE_MERGED_CONFIG
Resolving the failed step manually in the Engineering Lifecycle Management application pod
- Log in to the Red Hat OpenShift Container Platform web console.
- Go to .
- Select the project where you installed the Engineering Lifecycle Management instance from the Project list.
- The Pods page lists the Engineering Lifecycle Management application pods and Engineering Lifecycle Management operator pod information.
- Click the pod name where the upgrade step is failed.
- Go to the Terminal tab and run the following
command.
/elm/server/resolveUpgradeErr.sh <Resolve-code>Use the
Resolve codeinformation that you recorded when the failed step is identified.An example for resolving the failed step./elm/server/conf/resolveUpgradeErr.sh UPGRADE_MERGED_CONFIG