Known issues

This topic describes the known issues and limitations for Deployment Automation.

For a complete and up-to-date list of defects and fixes, see the Knowledge Base.

Install and upgrade

Deployment Automation 6.3.3 and later: Upgrading agents on Java 6 or 7 isn't supported from the user interface.

Deployment Automation 6.3.3 and later doesn't support the upgrade of Java 6 and 7 agents from the user interface.

Workaround: Use the 6.3.2 server to upgrade agents and agent JREs, or contact Support for assistance.

Deployment Automation 6.3.4: Agent installer stops responding on AIX when finished.

When installing a 6.3.4 agent in silent or console mode on an AIX system, the installer may stop responding when finished.

Solution: You can safely close/stop the installer. Your agent installation is complete.

Deployment Automation 6.3.2 and later: Server installer stops responding on AIX when finished.

When you run the DA server installer 6.3.2 or later on a heavily loaded AIX system, the installation wizard may not finish cleanly and may stop responding while displaying this message:

The InstallShield Wizard has successfully installed Deployment Automation. Choose Finish to exit the wizard. Press 3 to Finish or 5 to Redisplay [3]

Solution: Ignore the message and close/stop the installer. Your server installation is complete.

Upgrade to Deployment Automation 6.3.3: Agent relays may be displayed with incorrect status and version after upgrade.

After you upgrade the server to version 6.3.3 using the interactive installer, the agent relay may be displayed with the incorrect status and version in the Deployment Automation user interface.

Solution: After upgrading the server to 6.3.3, ensure that the agent relay is stopped, upgrade the relay, and start it. Then restart Common Tomcat.

Server upgrade from 6.3.1 to 6.3.2 and then to 6.3.3 on Windows: Common Tomcat may become corrupted because of extra comment tags in server.xml.

If you upgraded the server from 6.3.1 to 6.3.2 and then to 6.3.3 on Windows using the interactive installer, Common Tomcat may become corrupted because of duplicate comment tags in the server.xml file.

Solution: After upgrading to 6.3.3, remove extra comment tags next to the connector port 8409 block in server.xml. Change the opening tag from <!-- <!-- to <!-- and the closing tag from --> --> to -->. Save the changes and restart Common Tomcat.

Upgrade to Deployment Automation 6.3.2 or later on Windows: The interactive installer doesn't start correctly if only the HTTPS connector is active in server.xml.

When you attempt to upgrade to Deployment Automation 6.3.2 or later on Windows using the interactive installer, the installer may fail to start, displaying a Windows Installer package error. This happens because the server.xml file is missing an HTTP block.

Workaround 1: Before upgrading, add the HTTP block back to the server.xml file.

Workaround 2:

  1. Before upgrading, move the server.xml file to a different location and rename it, for example, to server.xml.bak. The default file location is:

    C:\Program Files\Micro Focus\common\tomcat\8.5\conf

  2. Upgrade Deployment Automation.
  3. Merge all the required changes in the server.xml file.

32-bit Windows NT 5.2 or earlier: Agents do not run with JRE 1.8.0_251 or later.

On 32-bit Windows NT 5.2 or earlier, Deployment Automation agents do not work with JRE 1.8.0_251 or later because of Java limitations. The agent's JRE cannot be upgraded to use JRE 1.8.0_265 bundled with the installation files.

Solution: Use JRE 1.8.0_250 or earlier.

Deployment Automation 6.2.1 and later: OpenJDK

Deployment Automation 6.2.1 and later uses OpenJDK. A server installation cannot be completed if the glibc dependency is missing.

Solution: Install the glib dependency for your operating system, for example:

CentOS: yum install glibc.i686

Ubuntu: apt-get install libc6.i686

Running Deployment Automation installer on CentOS.

To run the DA installer on a minimal CentOS, run this command in a terminal:

yum install bc

Deployment Automation 6.2.3 and later: z/OS agent cannot be upgraded from server. The z/OS agent cannot be upgraded from the Deployment Automation server 6.2.3 or later.
Pending approvals that are not completed before upgrade are revoked. Any pending approvals at the time of upgrade cannot be completed properly in the updated version due to architectural changes. Try to complete them before upgrading. Otherwise, after upgrading, you must rerun or reschedule the associated requests to initiate a new set of approvals.
Deployment Automation 6.1.1 and later: Agents may not come back online after server upgrade.

Due to changes to supported security protocols starting in version 6.1.1, Deployment Automation agents using earlier versions of Java, such as Java 6, may not be allowed to connect to the server after the upgrade.

If your agents do not come online after the server upgrade, upgrade them by following the instructions in Knowledge Base item S141622.

Installer page disappears when installing the agent on RedHat 7.3 that uses the Adwaita theme. If you are using the RedHat 7.3 with the Adwaita theme and try to install the Deployment Automation agent, the installer page disappears and you cannot complete the installation. This is due to the fact that the Adwaita theme is missing some objects used by installer. This works fine with other themes, such as Oxygen. For details on changing the theme, see Knowledge Base item S142064.

Back to top

General functionality

Deployment Automation 6.3.4 on UNIX: The server doesn't start if Common Tomcat is started from the root directory.

The Deployment Automation 6.3.4 server on UNIX doesn't start if you attempt to start the stopped server service from the root directory, for example: 

/opt/MicroFocus/da/common/tomcat/9.0/bin/startup.sh

Workaround: Change to the Common Tomcat's /bin directory and run the startup script: startup.sh.

Deployment Automation 6.3.3 and later: AIX agent installed with the Use Existing Java option may fail processes with parallel steps of the same plugin.

If you install an AIX agent 6.3.3 or later with the Use Existing Java option (java 1.8.0_181), and employ the agent to run a process that contains parallel steps of the same plugin, the process may stop responding, and large dump files may be created in the <agent>/core/var/work directory as a result.

Solution: Remove dump files and rerun the process. To avoid the issue, we recommend using the Java version bundled with your version of the Deployment Automation agent.

Deployment Automation 6.3.2 and later: Version import for Nexus Sonatype components is no longer working.

In Deployment Automation 6.3.2 and later, Nexus Sonatype no longer cuts off parts of the server URL. If you have used a URL with a relative path, the relative part now remains intact.

For example, in earlier versions, Nexus Sonatype converted the http://localhost:8080/nexus path into http://localhost:8080.

After upgrading to version 6.3.2 or later, you may need to reconfigure the components that use Nexus Sonatype as a source config type.

Deployment Automation 6.3.1 and later: Replication import may fail on Oracle.

If in Deployment Automation 6.3.1 or later replication import fails on Oracle with the error ORA-01000, the maximum open cursors limit has been exceeded. To change the limit on the database side, run this SQL query:

alter system set open_cursors = <limit_number>;

Deployment Automation 6.3 and earlier: Importing secure properties and property definitions, and passwords.

In Deployment Automation 6.3 and earlier, secure properties and property definitions, and passwords, are not resolved if they are imported from servers 6.3.1 or later.

Deployment Automation 6.3 and later: uBuild source configuration type not supported.

Starting from Deployment Automation 6.3, uBuild is no longer supported.

Workaround: Use the Deployment Automation API to develop your own plugin for uBuild.

Back to top

Integrations

Deployment Automation 6.3.4 and SBM 11.8/12.0: SBM SSO logout error when logging out of Deployment Automation.

When you log out of Deployment Automation 6.3.4 as an SBM 11.8 or 12.0 SSO user, the logout from SBM may fail.

For an SBM 12.0 SSO user, the following SBM error may be displayed:

CSRF token from HTTP request does not match with expected value

Workaround for SBM 12.0 SSO: Disable the CSRF token requirement in the fedsvr-core-config.xml file in your SBM 12.0 installation location:

  1. Open the fedsvr-core-config.xml file in the SBM Tomcat's WEB-INF\conf directory, for example:

    C:\Program Files\Micro Focus\SBM\Common\tomcat\server\default\webapps\idp\WEB-INF\conf\fedsvr-core-config.xml

  2. In the fedsvr-core-config.xml file, disable the CSRF token requirement by changing the AllowLogoutWithoutCSRFToken parameter to true.

  3. Restart SBM Tomcat.

Error configuring the ALM Solutions Connector 6.1.3 services when running encrypt.cmd to encrypt the almsernet properties.

When configuring the ALM Solutions Connector almsernet service, if you run encrypt.cmd to encrypt the almsernet_resource.properties files, the following error message is displayed:

Could not find or load main class com.serena.sernet.httpserver.util.Encrypt

Workaround: Edit the ..\webapps\almsernet\WEB-INF\encrypt.cmd file and change almsernet-8.1.0.jar to almsernet-8.1.2.jar.

Back to top

Browsers

Internet Explorer 11 displays HTTP error messages as generic friendly error messages.

If an HTTP error message is short, Internet Explorer 11 displays it as a generic friendly error message, making it difficult to troubleshoot the issue.

Solution: Disable the Show friendly HTTP error messages option in Internet Explorer's Internet Options > Advanced.

The user interface is not updated in Internet Explorer 11 after server upgrade.

When you have upgraded the server from version 6.2.2 or earlier to version 6.3.0 or later using the interactive or silent installation methods, and you open Deployment Automation in Internet Explorer 11, an old version of the user interface is displayed.

Solution: Refresh the page to update the user interface.

Chrome HTTPS connection fails on HP-UX servers.

You cannot connect to Deployment Automation through HTTPS in a Chrome web browser if your Deployment Automation server is installed on HP-UX. You can use other web browsers, such as Internet Explorer or Firefox, if you add an exception to the browser.

Workaround:

  1. In the server.xml file, find the commented out connector block that contains cipher attributes by searching for the word ciphers. The default directory for the file is:

    C:\Program Files\Micro Focus\common\tomcat\8.5\conf

  2. Insert the entire ciphers= attribute into the connector block that is being used for HTTPS, and save your changes.

  3. Restart Common Tomcat.

    The client now requests a WebSocket connection upon initial connection to the server. If you receive a WebSocket error, you may need to configure your proxy server to support the WebSocket connection. In some cases, the proxy server may need to be upgraded. For more information, see Knowledge Base item S141934.

Back to top

Connection issues

Connecting a 4.5.1 agent to the DA 6.3.2 server through HTTPS.

To connect a 4.5.1 agent to a 6.3.2 server through HTTPS, you must first manually upgrade the agent's JRE to version 1.8.

If the agent was installed with the bundled JRE, open the /jvm directory on your agent and replace all its contents with JRE 1.8 files.

Deployment Automation has limited support for IPv6 IP addresses.

If you are using IPv6 IP addresses on your network, you must use host name instead of IP address in Deployment Automation agent or agent relay configuration.

The following known issues exist for IPv6 addresses:

  • If you use IPv6 IP addresses in agent or agent relay configurations, you must use brackets around the address and with the colon character (:) escaped with a backward slash (\), for example, [fc00\:\:a1f\:2007].

    If you do not do this, the agent or relay does not connect and an error similar to the following message is displayed in the log:

    java.lang.IllegalArgumentException: hostname can't be null

  • If you run a process using the agent or agent relay configured using an IPv6 address, the process fails.
When a large number of agents are moved from one unidirectional agent relay to another, agents 6.1.1 and earlier may not automatically appear online.

When a large number of agents are changed to point to a different unidirectional agent relay, agents 6.1.1 and earlier may not come online automatically. They may be listed as CONNECTED or OFFLINE.

Solution: To bring agents online, click the Test icon in the Agents / Pools pane, or restart the agents.

Back to top

See also: