vAPP upgrade hangs on some nodes

Products

• CA Identity Suite

Issue/Introduction

After a successful 14.5.1 to CHF1 upgrade on the primary, non-DR nodes, the same upgrade hangs when run on the disaster recovery nodes. The are no failures or errors reported to the screen or logs.

Process status (ps -ef) and top commands show a chown process like the one below not progressing (not accruing CPU time).

chown -R config.config /home/config

Also, in the ca_vapp_main.log the install shows "Modifying permissions" as the recent activity.

drNode### doVappConfig [INFO] Modifying permissions

And, the logs show continuous looping on the clock sync check:

2025 Mar 05 00:00:09 server-#####7 check_cluster_clock_sync [WARN] Connecting to Remote Host(##.###.###.##4) for Current Date
2025 Mar 05 00:00:09 server-#####7 check_cluster_clock_sync [WARN] Remote Host(##.###.###.##4) Connection Closed after collecting Current Date
2025 Mar 05 00:00:10 server-#####7 check_cluster_clock_sync [WARN] Connecting to Remote Host(##.###.###.##1) for UTC Date
2025 Mar 05 00:00:10 server-#####7 check_cluster_clock_sync [WARN] Remote Host(##.###.###.##1) Connection Closed after collecting UTC Date
2025 Mar 05 00:00:server-#####7 check_cluster_clock_sync [WARN] Date on Current Machine - 1741150810 and Date on Remote Node ##.###.###.##1 - 1741150810
2025 Mar 05 00:00:10 server-#####7 check_cluster_clock_sync [WARN] Clock Diff - 0

Environment

IGA vAPP

Cause

The clock sync checks were found to have been caused by network mount share(s) servers not responding, ultimately causing the looping and failure of the upgrade to complete.

Resolution

Un-mount the network share(s), then re-apply the CHF patch.
After the CHF patch is applied re-enable the network share(s).

Additional Information

A fix, in the form of a timeout for the chmod that goes into the pre-init code, will be added to the installer. This fix will be available in a future CHF (Cumulative Hot Fix).