Welcome
Troubleshooting and Support
Learn how to troubleshoot some common issues with HCL DevOps Deploy (Deploy).
Troubleshooting the DevOps Deploy server and agents
Troubleshooting information that is specific to the server and agents is provided here.
Troubleshooting agent upgrade from the Web UI
You can troubleshoot errors that occur upgrading agents from the Web UI by performing a few checks.

Release Notes
This section includes what's new, defect fixes, and deprecations and removals in all releases.
System Requirements
This document includes information about the hardware, containers, prerequisite software, supported operating system, and database requirements with component level detail for the HCL DevOps Deploy (Deploy).
Getting Started
Quickly become productive with HCL DevOps Deploy (Deploy).
Installing
An HCL DevOps Deploy (Deploy) installation consists of a Deploy server, a database server, and at least one agent.
Upgrading and Migrating
Stay updated with latest features and functionalities by upgrading HCL DevOps Deploy (Deploy) server, agents, and relays. This section also provides instruction on how to migrate your Deploy instance.
Integrating
HCL DevOps Deploy (Deploy) supports integrations with other IBM® and HCL products, products from others, and certain cloud systems.
Administering
Learn how to administer settings in HCL DevOps Deploy (Deploy) elements and communication between the elements.
Managing Security
HCL DevOps Deploy (Deploy) uses a flexible team-based and role-based security model that maps to your organizational structure.
Modeling Software Deployment
Modeling software deployment in HCL DevOps Deploy (Deploy) includes configuring components and component processes and adding those components to applications. Then, you use processes to deploy the components to environments.
Deploying
Learn how to deploy applications in HCL DevOps Deploy (Deploy).
Reporting
Provides several different deployment and security reports.
Extending Product Function
Learn how to extend the function of HCL DevOps Deploy (Deploy).
Troubleshooting and Support
Learn how to troubleshoot some common issues with HCL DevOps Deploy (Deploy).
- Logging
  The server maintains logs for auditing and troubleshooting.
- Troubleshooting the DevOps Deploy server and agents
  Troubleshooting information that is specific to the server and agents is provided here.
  - Troubleshooting security and permissions
    To troubleshoot permissions, look carefully at the roles and teams of the user and the teams of the object that the user is trying to access.
  - Troubleshooting agent connections
    You can answer a number of questions to help isolate the issue behind problems with agents.
  - Troubleshooting agent upgrade from the Web UI
    You can troubleshoot errors that occur upgrading agents from the Web UI by performing a few checks.
  - Troubleshooting processes
    You can answer a number of questions to help isolate the issue behind problems and process failures.
  - Troubleshooting plug-ins
    Use the following procedures and tips to help troubleshoot plug-ins that you use with HCL DevOps Deploy (Deploy):
- Troubleshooting DevOps Deploy when running as a container
  When you install HCL DevOps Deploy (Deploy) server by using the provided Helm chart, two containers are created. The first is named init that performs some initialization steps, including initialization of your database. The second is hcl-launch-prod, which is the main server container. You can debug issues by checking the logs of each of these containers.
- Troubleshooting problems on z/OS®
  To troubleshoot problems on agent computers that are running IBM® z/OS®, examine the agent log files.
- Performing AI analysis on failed deployments
  You can perform AI analysis on failed deployments to identify the root cause of the failures and troubleshoot them easily.
Security Considerations
You can act to ensure that your installation is secure and set up user access controls.

Troubleshooting agent upgrade from the Web UI

You can troubleshoot errors that occur upgrading agents from the Web UI by performing a few checks.

To resolve errors, perform the following checks:

Verify that the air-agentupgrade.jar file is downloaded from the <serverInstallDir>/opt/ directory to the <agentInstallDir>/bin/ or <agentInstallDir>/var/upgrade/ directory.
In version 7.2.x and earlier, the air-agentupgrade.jar file is downloaded to the <agentInstallDir>/bin/ directory. Starting with 7.3.x and later versions, the air-agentupgrade.jar file is downloaded to the <agentInstallDir>/var/upgrade/ directory.
Note:
If the air-agentupgrade.jar file is missing, you must verify that it exists on the <serverInstallDir>/opt/ directory. If the file exists, you must check for network connectivity issues or write permission errors on the agent.

Verify that the agent unzipped the air-agentupgrade.jar file into a specific sub-directory if the air-agentupgrade.jar file is present in the download path.

The following table lists the download and unzipped locations of the air-agentupgrade.jar file for each version of Deploy:


Version	Download location	Unzipped location
7.2.x and earlier	<agentInstallDir>/bin/	<agentInstallDir>/bin/agent-upgrade/
7.3.x and later	<agentInstallDir>/var/upgrade/	<agentInstallDir>/var/upgrade/unpack/

If the air-agentupgrade.jar file is not created and unzipped in the specified location, then you must check for user permission issues.

Note:

If you use Security-Enhanced Linux (SELinux), it might block the agent user from creating directories. To resolve this issue, you must temporarily set SE-Linux to permissive mode.

Refer to the logs for specific error codes if the upgrade fails or stalls for any other reasons.
In version 7.2.x and earlier, you must check the <agentInstallDir>/bin/upgrade.out log file. In version 7.3.x and later, you must check the <agentInstallDir>/var/log/upgrade.log file. Starting with version 8.1.0, you can view or download the upgrade log directly from the Log tab of the agent in the Web UI.
If the log exists, you must review it for the Permission Denied or File Not Found errors.