Operational Defect Database
BugZero updated this defect 58 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
VMware | 67139
Automatic upgrade stops responding on some of the steps on the Update tab of VAMI
Last update date:
3/22/2024
Affected products:
vRealize Automation
Affected releases:
7.47.57.3
Fixed releases:
No fixed releases provided.
Description:
Symptoms
The automatic upgrade stops responding on some of commands/steps listed on the VAMI > Update tab. Note: This screenshot is only for illustration purpose. When examining the respective IaaS node's Management Agent All.log file, there are no errors.The last triggered commands from the time of the upgrade are all completed successfully. Note: This issue is applicable only if the following conditions are true: There has been a VA failover event at any time before the upgrade,so that the former primary is now a replicaUpgrade is from version older than 7.4 to version 7.5 (e.g. 7.3.1 --> 7.5)The replica upgrade has failed in the very beginning (e.g. at validation) so replica node is still the old version. The IaaS automatic Upgrade is started, although the replica is not yet upgraded (this is allowed).
Cause
This issue occurs because the MAs continue to communicate with the Replica VA node which is still the old version. The upgrade script is triggered on the Primary VA node which is already the new version.
Resolution
Currently, there is no resolution.
Workaround
To work around this issue, use one of these options:Option 1:Ensure the Replica node (or all replica nodes if more than one) are upgraded before proceeding with the automatic IaaS upgrade.Note: If not explicitly excluded (by executing touch /tmp/disable-iaas-upgrade), the IaaS upgrade will start automatically after rebooting the primary VA (when the upgrade has completed).Option 2: Stop all Management Agent services on all IaaS nodes.Open their respective ManagementAgent.exe.config files and ensure the list of VAs in the <managemetEndpoints> section starts with the current Primary VA.Restart the Management Agents and trigger the automatic IaaS upgrade. Option 3:Upgrade IaaS manually using the IaaS installer that can be downloaded from the VAMI installer download page.
