This documentation supports an earlier version of BMC Helix IT Service Management on-premises deployment.To view the documentation for the latest version, select 23.3.04 from the Product version picker.

Troubleshooting deployment pipeline failure issues

The HELIX_ONPREM_DEPLOYMENT deployment pipeline that you use to perform BMC Helix Service Management installation consists of the various pipelines, such as HELIX_PLATFORM_DEPLOY, HELIX_NONPLATFORM_DEPLOY, and HELIX_SMARTAPPS_DEPLOY. During installation, if any of these pipeline fails, you can troubleshoot the pipeline failure issue, and rebuild the pipeline.

Related topics

Viewing-and-collecting-logs-by-using-the-Support-Assistant-tool

Troubleshooting-the-installation-errors

To troubleshoot failure due to incorrect parameter values

If a pipeline fails due to incorrect parameter values, perform the following steps:

  1. On the Jenkins UI, navigate to the pipeline where failure occurred.
  2. In the pipeline where the failure occurred, in the Build History pane, select the latest build, and click Console Output.
  3. On the Console Output page, check the logs to find the reason for the failure.
  4. Navigate to the HELIX_ONPREM_DEPLOYMENT pipeline.
  5. From the Build History pane, select the latest job, and click Rebuild.
  6. Specify the correct parameter values.
    For example, if the HELIX_PLATFORM_DEPLOY pipeline fails due to incorrect FTS_ELASTICSEARCH_PORT value, specify the correct FTS_ELASTICSEARCH_PORT value.
  7. Select the HELIX_GENERATE_CONFIG pipeline.
    Make sure that you do not select any other pipeline.
  8. Click Rebuild.
  9. Rerun the failed pipeline.
    1. Navigate to the pipeline where the failure occurred.
    2. In the failed pipeline, in the Build History pane, select the latest build, and click Rebuild.
    3. On the Rebuild page, select the ReRun check box , and click Rebuild.
      The pipeline starts running from the instance where it stopped due to the failure.

To troubleshoot failure due to environment issues

If a pipeline fails due to environment issues such as Kubernetes cluster not reachable, PVC not mounted successfully, and insufficient resources to start a container, perform the following steps:

  1. In your Jenkins server, run the following command to identify the issue:

    kubectl get events -n <Innovation Suite namespace>
  2. Debug and fix the issue.
  3. Rerun the failed pipeline.
    1. On the Jenkins UI, navigate to the pipeline where the failure occurred.
    2. In the failed pipeline, in the Build History pane, select the latest build, and click Rebuild.
    3. On the Rebuild page, select the ReRun check box , and click Rebuild.
      The pipeline starts running from the instance where it stopped due to the failure.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*