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

How to update VMware Cloud Foundation to prevent unassigned hosts from needing to be re-upgraded after a workload domain deletion (59337)

Last Updated: 7/28/2021Categories: How toTotal Views: 2586Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

An unassigned host has been upgraded to allow it to be added to a workload domain.

When the workload domain is deleted, the host version is reverted to the one at which it was imaged (pre-upgrade).

The unassigned host must be upgraded again prior to inclusion in a new workload domain.

Purpose

This article provides instructions for modifying VMware Cloud Foundation 2.3.1/2.3.2.x to prevent an unassigned host that has been upgraded from needing to be upgraded again after a workload domain is deleted.

Resolution

Download the attached 59337_vcf-unassigned-hosts.zip file.

Use a file transfer utility to copy the 59337_vcf-unassigned-hosts.zip file to the /tmp folder on the SDDC Manager Controller virtual machine.

Log in to the SDDC Controller VM as the root user.

Issue the following commands to create a backup of the current sos utility and then update the sos utility:

cp -rfp /opt/vmware/sddc-support /opt/vmware/sddc-support.$(date +%m%d%y)
unzip -d /tmp/ /tmp/59337_vcf-unassigned-hosts.zip
cd /tmp/vcf-unassigned-hosts
chmod +x setup.sh
./setup.sh

Note: You will see output similar to the following:

Start compiling all py files ...
Removing all py files ...
Copying files to SOS directory
Setup completed successfully

Issue the /opt/vmware/sddc-support/sos --upgrade-unassigned-host command to upgrade the host to the desired version.

Note: You can view the progress of the upgrade on the Lifecycle page of the SDDC Manager UI. Multiple unassigned host upgrades can be scheduled at the same time. They will run sequentially in the UI.

Issue the /opt/vmware/sddc-support/sos --config-bundle-backup to create a new bootbank and configuration backup for the host(s) upgraded in Step 5:

Note: You will see output similar to the following:

Welcome to Supportability and Serviceability(SoS) utility!
NOTE : SoS may fail if workflow is undergoing password rotation operation, run SoS when no workflows are in flight.

Logs : /var/tmp/unassigned-host-lcm
+-----+------+------------+----------------+---------------+-----------------+
| SL# | NODE | Rack Name  |  Domain Name   |  Base Version | Current Version |
+-----+------+------------+----------------+---------------+-----------------+
|  1  | R1N3 | gss-vxrack |      MGMT      | 6.5.0-7967591 |  6.5.0-9298722  |
|  2  | R1N2 | gss-vxrack |      MGMT      | 6.5.0-7967591 |  6.5.0-9298722  |
|  3  | R1N1 | gss-vxrack |      MGMT      | 6.5.0-7967591 |  6.5.0-9298722  |
|  4  | R1N0 | gss-vxrack |      MGMT      | 6.5.0-7967591 |  6.5.0-9298722  |
|  5  | R1N5 | gss-vxrack | - UNASSIGNED - | 6.5.0-7967591 |  6.5.0-9298722  |
|  6  | R1N4 | gss-vxrack | - UNASSIGNED - | 6.5.0-7967591 |  6.5.0-9298722  |
|  7  | R1N7 | gss-vxrack | - UNASSIGNED - | 6.5.0-7967591 |  6.5.0-9298722  |
|  8  | R1N6 | gss-vxrack | - UNASSIGNED - | 6.5.0-7967591 |  6.5.0-9298722  |
+-----+------+------------+----------------+---------------+-----------------+

Select ESXi for Config backup, ESXi : R1N5

* Backup ESXi Config Bundle : R1N5

* Creating state backup...

* Remove existing backup for ESXi : R1N5

* Uploading bootbank and state backup...

Logs : /var/tmp/unassigned-host-lcm
Log file : /var/tmp/unassigned-host-lcm/sos.log

Notes:

This entire process can be used for hosts returned to the unassigned pool after a workload domain is deleted.

Repeat Step 6 for all unassigned hosts that have been upgraded

Related Information

If vSphere updates are applied after this process is implemented, it may be necessary to go through it again as the hosts in a workload domain that are deleted will be reverted to the version they were at prior to being added to a workload domain.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

59337_vcf-unassigned-hosts.zip

Additional Resources

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

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Cloud Foundation

Related Versions:

VMware Cloud Foundation 2.3.x

Take Our Survey

Support Assistant