For a complete and up-to-date list of defects and fixes found in the latest release of Deployment Automation, see the Knowledge Base.
Here are the issues known to exist at the time of release:
Upgrade to Deployment Automation 6.3.3: After the upgrade, agent relays may be displayed with incorrect status and version.
After you upgrade the server to 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.
Windows: After the server upgrade from 6.3.1 to 6.3.2 and then to 6.3.3, 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
<!--and the closing tag from
-->. Save the changes and restart Common Tomcat.
Windows: When attempting to upgrade Deployment Automation, the interactive installer doesn't start correctly if only the HTTPS connector is active in server.xml.
Deployment Automation 6.3.2 and later: When you attempt to upgrade Deployment Automation 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 doesn't contain an HTTP block.
Workaround 1: Before upgrading, add back the HTTP block to the server.xml file.
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
- Upgrade Deployment Automation.
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.
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 Deployment Automation web interface is not updated in Internet Explorer 11 after server upgrade.
Deployment Automation 6.3.0 and later: When you have upgraded the server from version 6.2.2 and earlier to version 6.3.0 and 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.
AIX: installation wizard stops responding when finished.
Deployment Automation 6.3.2 and later: When you run the DA server installer 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 
If this happens, you can safely abort the installer. Your server installation is complete.
Version import for Nexus Sonatype components is no longer working.
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.
Connecting a 4.5.1 agent to the DA 6.3.2 server through HTTPS.
Deployment Automation 6.3.2: 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.
Replication import fails on Oracle.
Deployment Automation 6.3.1 and later: If 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>;
Importing secure properties and property definitions, and passwords.
Deployment Automation 6.3 and earlier: secure properties and property definitions, and passwords, are not resolved if they are imported from servers version 6.3.1 or later.
uBuild source configuration type.
Deployment Automation 6.3 and later: uBuild is no longer supported.
Workaround: Use the Deployment Automation API to develop your own plugin to support uBuild.
Deployment Automation 6.2.1 and later uses OpenJDK. A server installation cannot be completed if the
glibcdependency is missing.
Solution: Install the
glibdependency for your operating system, for example:
yum install glibc.i686
apt-get install libc6.i686
Running DA installer on CentOS.
To run the DA installer on a minimal CentOS, run this command in a terminal:
yum install bc
z/OS agent cannot be upgraded from server.
Deployment Automation 6.2.3 and later: The z/OS agent cannot be upgraded from the Deployment Automation server.
Pending approvals 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. You should complete them before upgrading if possible. Otherwise, after upgrading, you must rerun or reschedule the associated requests to initiate a new set of approvals.
Deployment Automation has limited support for IPv6 IP addresses.
If you are using IPv6 IP addresses on your network, you must use hostname instead of IP address in Deployment Automation agent or agent relay configuration.
Here are the known issues 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,
If you do not do this, the agent or relay does not connect and an error similar to the following 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.
Chrome web browser HTTPS connection fails on HP-UX server.
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.
In the server.xml file, find the commented out
connectorblock 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
- Insert the entire
ciphers=attribute into the
connectorblock that is being used for HTTPS, and save your changes.
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.
Agents may not come back online after server upgrade.
Deployment Automation 6.1.1 and later: 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.
When a large number of agents are moved from one unidirectional agent relay to another, agents of versions earlier than 6.1.2 may not automatically appear online.
When a large number of agents are changed to point to a different unidirectional agent relay, agents of versions earlier than 6.1.2 may not come online automatically. They may be listed as CONNECTED or OFFLINE.
Solution: To bring them online, click the Test icon in the Agents / Pools pane, or restart the agents.
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.
Error configuring the ALM Solutions Connector 6.1.3 services when running
encrypt.cmdto encrypt the almsernet properties.
When configuring the ALM Solutions Connector
almsernetservice, if you run
encrypt.cmdto encrypt the almsernet_resource.properties files, the following error occurs:
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.