6.2.7.3 – May 23, 2018

Fixes in this Release

PI94915 PROCESS EDITOR CAN FREEZE BROWSER IF PROCESS CONTAINS A NOTE UNDER SOME CIRCUMSTANCES
PI92552 SOME LINUX/UNIX VARIANTS FAIL WITH “./INSTALL-AGENT.SH: 21: ./INSTALL-AGENT.SH: FUNCTION: NOT FOUND”
PI92285 PROCESSES THAT REFERENCE NULL PLUGINCOMMANDS WILL BREAK THE PROCESSPLUGINUSAGEMETADATAGENERATOR
PI92116 RUNNING HISTORY CLEANUP WITH AN EXISTING ENVIRONMENT APPROVAL TASK ON AN OLDER GHOSTED ENVIRONMENT BREAKS THE WORK ITEMS PAGE
PI91830 CANNOT VIEW APPLICATION LOG WITH BLANK NOTE STEP PRESENT
PI88236 AGENT UPGRADE FAILS ON 32-BIT OS
PI84809 DEPLOYMENT HISTORY CLEANUP UI PROGRESS BAR STUCK
PI83815 USERS NEED VIEW PERMISSION TO TOP LEVEL RESOURCES
PI83932 CREATE COMPONENT STEP DOESN’T SET THE BASEPATH PROPERTY FOR FILE SYSTEM SOURCE CONFIG TYPE
PI80376 UC VERSION IMPORT USER MISSING PERMISSION FOR DOCKER
PI80130 APPLICATION TEMPLATE PROCESS CAN DEPLOY INDIVIDUAL COMPONENT DEPLOYMENTS IF THEY USE CLIPBOARD
PI74398 ENVIRONMENT PROPERTY MISMATCH IN CONFIGURATION TAB
PI71048 ISSUES SCHEDULING A RECURRING SECURITY REPORT
PI70971 RESOURCE FILTER DOES NOT WORK WHEN CHOOSING BASE RESOURCE WHEN CREATING ENVIRONMENT FROM BLUEPRINT
PI69502 CANNOT VIEW COMPONENT CONFIGURATION PAGE
PI67025 SUDO IMPERSONATION FAILING WITH NULLPOINTEREXCEPTION
PI57779 REMOVING IMPERSONATION DOES NOT CLEAR DEFAULT IMPERSONATION SETTINGS
PI45937 ERROR WHEN RUNNING UCD INSTALLATION SCRIPT

Known Problems and Workarounds

To search for additional post-release issues that IBM Rational Support documented, visit the IBM Support portal.

Upgrade Notes

 

Starting in 6.2.7.1

API-breaking changes have been made to the supported REST endpoints that set properties in UCD, including the addEnvironmentProperty, setAgentProperty, setApplicationProperty,setComponentEnvironmentProperty, setComponentProperty, setComponentVersionPropDef, setEnvironmentProperty,setResourceProperty, setSystemConfiguration, setSystemProperty, and setVersionProperty endpoints. Any scripts that need to set properties on components, agents, the system, processes, process requests, applications, or environments will need to be adjusted. Consult the documentation for the new syntax.

Also, because of these API changes, the plugins that set properties in UCD are not backwards compatible. In the following list of plugins, any plugin version before the version listed is not compatible with UCD 6.2.7.1 or later, and and any plugin version after the version listed is not compatible with 6.2.7.0 or earlier. On upgrading to UCD 6.2.7.1, the plugins will automatically be updated to a supported version. However, using old versions of processes that are locked in snapshots or downgrading the UCD plugin version may cause steps to fail.

Plugin 6.2.7.1+ compatible versions
IBM UrbanCode Deploy Applications 77+
IBM UrbanCode Deploy Components 71+
IBM UrbanCode Deploy Environments 77+
IBM UrbanCode Deploy Resources 74+


Starting in 6.2.5.2

Starting the server for the first time may take longer than usual. For very large installations, allow an extra hour for the first server startup. Subsequent startups will take the regular amount of time.

Users now do not receive notifications based on their membership in a role on the System Team. Users will have to be added to the correct role on a different team as well to receive notifications.

The server now deletes all contents of the var/temp directory on server startup.

Starting in 6.2.5.1

Process requests from deleted environments will now be deleted. To keep process requests from deleted environments, add this property to the installed.properties file: com.urbancode.ds.cleanup.HistoryCleanup.disableDeletedEnvironmentCleanup=true

Starting in 6.2.5.0

The UCD_SESSION_KEY header has been renamed to UCD_CSRF_TOKEN. The previous name is also accepted until 6.3 when it will be removed from the product.

Users now require the “Execute” permission on agents in order to run processes against them. All existing user roles will receive this permission when upgrading from a version before 6.2.5.0. When upgrading, ensure that any user that needs to execute processes is on the same team as the agents required to run those processes.

Starting in 6.2.4.0

You must upgrade Agent Relays when upgrading from a version below 6.2.4.0. Also, the TLS protocol 3DES is no longer supported.

After upgrading from before 6.2.4.0, users will not be able to view or delete agent relays until they have been granted permission to those relays. Relays that existed before the upgrade are only added to the System Team by default. For users to view agent relays, a user with Manage Security permission should give the correct roles the new For relays that existed before the upgrade, a user with Manage Security permissions will have to add the agent relays to the correct teams and give the correct roles the Agent Relay view and edit permissions.

When upgrading an IBM UrbanCode Deploy agent, end-to-end JMS encryption will automatically be enabled on all agents. In order for agent communication to function properly with end-to-end encryption enabled, the IBM UrbanCode Deploy server and agent clocks need to be synchronized to within a few minutes. To disable this feature, add the line agent.jms.disable_full_encryption=true” to the agent’s conf/agent/installed.properties file before upgrading the agent.

Starting in 6.2.3.0

If you are upgrading from version 6.2.3.0 and earlier, servers and relays must be upgraded at the same time. Agents connected through relays may not connect successfully until both server and relay are upgraded. This is due to an incompatibility between versions of an library used by UCD.

Starting in 6.2.3.0, authentication tokens will be obfuscated in the UI and REST API after their initial creation. Scripts and users will only be able to retrieve the full authentication token immediately after creating it.

The silent install of the IBM UrbanCode Deploy server hangs when prompting for the value of the server installation directory (install.server.dir). To workaround the problem, run the following instead of calling ./install-server.sh directly:
echo "" > answerFile.txt echo "" >> answerFile.txt ./install-server.sh < answerFile.txt (or install-server.bat < answerFile.txt for Windows installations)

Starting in 6.2.2.0

The IBM UrbanCode Deploy server and agent relays now require a Java Runtime Environment (JRE) or Java Development Kit (JDK) version 8. If you are updating or changing the JRE to the latest version, see
Changing or updating the JRE of servers and Updating the JRE location for agent relays for instructions. For documentation on the IBM JRE, see IBM SDK, Java Technology Edition.

Starting in 6.2.1.1

To ensure that all secure property values are obscured, the values of all properties in the history for existing deployments are obscured. In the deployment history for deployments that you run after you upgrade, only secure properties are obscured in the logs.

New security features erase old component version import logs to hide secure information. If you want to keep the logs, in the installed.properties file, set the com.urbancode.ds.cleanup.sourceConfig.fullCleanupSkip property to true.

Plan & Prepare

For fixes contained in this release, and any known issues, review the release notes.

For supported platforms and requirements, see the reports that can be dynamically generated using the Software Product Compatibility Reports (SPCR) tool.

Note: Some supported plug-ins have system requirements that vary from the core product. Information on system requirements for individual plug-ins is available on the download page for that plug-in.

To get started quickly to try the software, IBM UrbanCode Deploy is shipped with an Apache Derby database. Apache Derby deployments are not supported for production environments. As you plan your production topology, review the installation guide.