During a PAM cluster upgrade from 4.3 to 4.3.1, one or more nodes show "Complete" in the Upgrade stage when the process is actually still running. This persists until the node from where the live upgrader was launched, the upgrade driver node, reboots. Once the driver node is back up and the live upgrader UI available again, it is observed that the problem nodes resume the Upgrade stage, go through the expected reboot and complete the upgrade successfully.
CA Privileged Access Manager (PAM) 4.3 multi-site cluster.
Intermittent network drops (TCP connection closed) can cause the upgrade driver to skip further status checks and display status "Complete" for affected nodes. This is likely to be observed only with cluster nodes in remote sites. When the driver node comes back from its reboot and checks on the status of all nodes, it finds that the affected nodes have not completed the upgrade yet and gets them to resume it.
This issue is resolved in PAM 4.3.2.
If you observe this problem and it doesn't fix itself as described above, contact Support.