Autopatch not working for Secondary IP

Products

• CA Automic Dollar Universe

Issue/Introduction

Error Message :
Messages in universe.log while the autopatch is launched:

|INFO |X|IO |pid=11950.139733833225984| u_io_thread_auto_update | Launching DUAS-UPDATE-LINUX64-6.8.41 update: /apps/du/600/TST600/bin/uxdqmlan
|INFO |X|IO |pid=11950.139733833225984| u_io_thread_auto_update | Update script executed.
|ERROR|X|DQL|pid=12220.140542965565184| o_connect_auth | k_connect_auth_timeout returns error [200]
|ERROR|X|DQL|pid=12220.140542965565184| o_connect_auth | k_connect_auth_timeout returns error [200]
|ERROR|X|DQL|pid=12220.140542965565184| u_io_callsrv_connect_r | Error connecting to target IO server: Errno syserror 111: Connection refused (connect returns error)
|ERROR|X|DQL|pid=12220.140542965565184| uxdqmlan | Cannot connect to IO server TST600 X: local

On a Linux VM with two different network cards, where DUAS has been installed as a Cluster with the secondary IP / secondary hostname, the autopatch does not work as it tries to connect to the primary IP address. 

The Autopatch status remains in Upload In Progress, and the uxdqmlan generates a defunct process.

Environment

OS: All Linux/Unix

Cause

Cause type:
Defect

Resolution

Update to a fix version listed below or a newer version if available.
If node comes from version inferior to 6.9.01, the workaround needs to be applied first.

Fix Status: Released

Fix Version(s):
Component: Application.Server
Dollar Universe 6.9.01 - Available

Additional Information

Workaround :
Two options:
1. Setting the variable U_CLUSTER to N before launching the autopatch and setting it back to Y after the upgrade.
2. Upgrading the node with the kit from the system and not via the autopatch.