Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

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

"Upgrade failed" in VAMI Cluster tab for IaaS component (78509)

Last Updated: 9/24/2021Categories: TroubleshootingTotal Views: 4733Language:
English

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Symptoms

After a failed automatic IaaS upgrade attempt IaaS is upgraded successfully with the manual IaaS installer.

For one or more IaaS component you see:

Upgrade failed
or

Default Web Site Upgrade to 7.6.0.16195 pending

Cause

The Upgrade failed warning indicates automatic IaaS upgrade has failed for the respective IaaS component and the node it resides on has not been reverted.

This status would prevent subsequent automatic upgrades as the environment might be in a corrupted state.

In general, it is always recommended to revert the node where the IaaS upgrade has failed before retrying the upgrade. This is especially valid in case of failed primary web node upgrade. In that case the IaaS MS SQL database must also be reverted to its pre-upgrade snapshot or back-up.

Resolution

Before clearing the Failed status it is important to understand how and why the automatic upgrade failed and to make sure that the manual upgrade was indeed successful and environment is in a healthy state.

The logs from the automatic upgrade are found on the primary appliance at /opt/vmware/var/log/vami/upgrade-iaas.log and then check the Management Agent All.log file on the node where it failed.

The Upgrade failed state for IaaS components can be cleared in the registry.

Locate the respective IaaS component key under one of the following registry locations and expand its entries.

"HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\VMware, Inc.\VMware vCloud Automation Center Server"
"HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\VMware, Inc.\VMware vCloud Automation Center WAPI"
"HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\VMware, Inc.\VMware vCloud Automation Center DEM"
"HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\VMware, Inc.\VMware vCloud Automation Center Agents"

Locate the ComponentCondition registry entry and delete it, or modify its value to Completed.

The change will be visible in VAMI Cluster tab immediately after the next Management Agent ping report (by default every 30 seconds).

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
在 vSphere Lifecycle Manager 中的 "独立组件" 视图下看不到组件 (78538)

KB
•
无法在 HTML 5 或 Flex UI 中加载虚拟机详细信息，虚拟机详细信息的加载似乎已停滞或“硬件”选项卡为空 (78485)

KB
•
vRealize Operations 8.x 及更高版本中的 Photon OS 如何利用交换空间。 (78489)

KB
•
HTML 5 または Flex ユーザー インターフェイスで仮想マシンの詳細をロードできない、仮想マシンの詳細のロードが停止しているように見える、または [ハードウェア] タブが空白のように見える (78485)

Results 1-4 of 4

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