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

Patching of VMware vCenter Server Appliance 6.7.x (with vCenter High Availability) enabled fails (55938)

Last Updated: 2/27/2024Categories: Best PracticesTotal Views: 19859Language:
Portuguese (Brazil)JapaneseSpanishEnglish

11 like this article

Subscribe to get an email
newsletter with new updates

11 people found this helpful Please provide article feedback:

Symptoms

Patching of VMware vCenter Server Appliance 6.7.x (with vCenter High Availability) enabled fails.

Purpose

This article provides steps to follow before patching vCenter HA enabled vCenter Server Appliance 6.7 systems to different update lines.

Cause

This issue occurs due to a DB schema change while patching of vCenter HA enabled on VCSA 6.7.x.

Resolution

This issue is resolved in VMware vCenter Server 6.7 Update 3b, available at VMware Downloads.

Note: Before proceeding with the patching, ensure that the vCenter Server FQDN is properly resolvable and there are no duplicate DNS entries for the FQDN in the DNS Server due to a known issue. For more information, see Clean up duplicate DNS records of vCenter (76406) .

This is a known issue affecting patching of vCenter HA enabled on vCenter Server 6.7.U3a and earlier patches of 6.7, please refer the below table for more information.

Path (vCenter HA enabled)

Behavior (Patching Support)

VCSA67GA to VCSA 67U1x,67U2x,67U3x

Not Supported

VCSA67U1x to VCSA 67U2x,67U3x

Not Supported

VCSA67U2x to VCSA 67U3x

Not Supported

VCSA67U3 to VCSA 67U3a

Not Supported

VCSA67U3 to VCSA 67PU3b

Supported

VCSA67U3a to VCSA 67U3b

Supported

Workaround

To work around this issue for unsupported paths:

vSphere Client

Select the vCenter Server object.

Navigate to Configure > vCenter HA.

Select the option Remove vCenter HA. This automatically shutdown and delete the passive and witness node.

Patch the vCenter Server.

vSphere Web Client

Select the vCenter Server object.

Navigate to Configure > vCenter HA.

Click Edit.

Select the option Remove vCenter HA. This automatically shutdown and delete the passive and witness nodes if using the Basic Deployment. If using an Advanced deployment, you need to manually power off and delete the passive and witness nodes.

Patch the vCenter Server.

For more information see:

Patch a vCenter High Availability Environment

Patching the vCenter Server Appliance by Using the Appliance Management Interface

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Portuguese (Brazil)JapaneseSpanishEnglish

Attachments

Additional Resources

KB
•
VMware Workstation Pro 12.x へのゲスト OS としての Windows 10 のインストール (2128790)

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

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vCenter Server Appliance

Related Versions:

VMware vCenter Server Appliance 6.7.x

Take Our Survey

Support Assistant