Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Automatic IaaS upgrade to vRA 7.6 fails on upgrade-server task for primary web node - all IaaS server components are already vRA 7.6 (70684)

Last Updated: 5/5/2020Categories: TroubleshootingTotal Views: 4359Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

The automatic upgrade to 7.6 fails on upgrade-server task for primary IaaS web node and the error does not contain a recommendation to revert the node and the IaaS database.
The "revertRequired" field in the "/opt/vmware/var/log/vami/upgrade-iaas.json" output file is "false" for the command that failed.
The VAMI Cluster tab displays all server components (Database, Website, Model Manager Web, Model Manager Data, Wapi, Manager Service) that reside on the primary node as upgraded to the new version.

Note: This does not include DEM and Proxy agent components, if any reside on the same node, since they are being upgraded on a later stage with a different command and are expected to still be the old version at this point.

Cause

That is not an uncommon situation and is usually caused by connectivity issues between primary IaaS web node and CAFE and/or wrong load balancer settings.

Resolution

This is one of the situations where retry without reverting anything is allowed.
After troubleshooting the failure and making sure the root cause is not present anymore - upgrade could be retried but that must happen manually - since all server components on the primary node are already upgraded and the automatic upgrade will not start an upgrade command for that node.

To retry the primary web upgrade manually execute the following steps:

SSH to primary VA.

Execute "vra-command list-nodes" (or its verbose versions "vra-command list-nodes --components") to get the node ID of the primary web node.

Execute "vra-command execute --node <primary_web_node_id> upgrade-server" for upgrades from 7.x

or,

Execute "vra-command execute --node <primary_web_node_id> upgrade-server --VraAddress"<vRA_LB_hostname>" --VraWebCertificateThumbprint "<vRA_certificate_thumbprint>" --DefaultTenant "<vRA_default_tenant>" --VidmAdminUser "administrator" --VidmAdminPassword "<vIDM_admin_password>"" for upgrades from 6.2.x where:

vRA_LB_hostname - is the hostname of the VA load balancer (or the VA hostname if not in HA) - this can be retrieved by executing "/usr/sbin/vcac-vami host info" command on the primary VA

vRA_certificate_thumbprint - is the thumbprint of the vRA certificate without spaces and dashes and with capital letters

vRA_default_tenant - is the default vRA tenant and can be retrieved from the following configuration file on the primary VA "/etc/vcac/security.properties" - set under "vmidentity.websso.tenant" key

vIDM_admin_password - is the password for the vIDM administrator

The manual server upgrade will continue from the last successful post upgrade task. If the command fails on the same post-upgrade task as the last time or moves past it at fails on a subsequent one (this could be monitored in the Management Agent All.log file on the primary web node) - it could be retried manually the same way.

Note: In case retrying does not resolve the problem and the failure is consistent - revert of the primary web node and the IaaS MS SQL Server database might still be necessary.

After the primary web server upgrade is completed manually - the automatic IaaS upgrade can be re-triggered by executing "/usr/lib/vcac/tools/upgrade/upgrade" script on the primary VA and it will skip the already upgraded node(s).

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
コンプライアンス スコアが、vRealize Operations Manager 7.5 の分析ノードによって異なる (70665)

KB
•
如何调整 vRealize Automation postgres 数据库 ebs_event 表的清除时间间隔 (70759)

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Aria Automation

Related Versions:

VMware vRealize Automation 7.6.x

Take Our Survey

Support Assistant