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

vSAN -- File Services -- File Service VM (= FSVM) reports: "Virtual Machine Consolidation Needed Status" (79024)

Last Updated: 2/23/2024Categories: TroubleshootingTotal Views: 5219Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

This issue affects the automated generated File Service VMs (= FSVM).
Reference:
"When you configure vSAN file service, vSAN creates a single VDFS distributed file system for the cluster which will be used internally for management purposes.
A file service VM (FSVM) is placed on each host. The FSVMs manage file shares in the vSAN datastore. Each FSVM contains a file server that provides both NFS and SMB service."

A File Service VM (= FSVM) shows the Warning: "Virtual Machine Consolidation Needed Status"

The vCenter /var/log/vmware/vsan-health/vmware-vsan-health-service.log indicate that the destroy of the File Service VM (= FSVM) failed by showing similar entries like the following:

2020-04-21T06:05:20.787Z ERROR vsan-mgmt[35201] [VsanEamUtil::DestroyEamAgentVMs opID=W79787] Failed to destroy agent VM 'vim.VirtualMachine:vm-333' on host host-108
Traceback (most recent call last):
File "/build/mts/release/bora-16051639/bora/build/vcenter/release/pkg/vsanmgmt/stage/usr/lib/vmware-vpx/vsan-health/pyMoVsan/VsanEamUtil.py", line 734, in DestroyEamAgentVMs
File "/usr/lib/vmware/site-packages/pyVim/vimutil.py", line 30, in InvokeAndTrack
return WaitForTask(task)
File "/usr/lib/vmware/site-packages/pyVim/task.py", line 140, in WaitForTask
raise info.error
VsanVmomiPatcher.vim.fault.InvalidPowerState: (vim.fault.InvalidPowerState) {
msg = 'The attempted operation cannot be performed in the current state (Powered on).',
faultCause = <unset>,
faultMessage = (vmodl.LocalizableMessage) [],
requestedState = 'poweredOff',
existingState = 'poweredOn'
}
Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Cause

This issue occurs when the File Service Remediation Service detected one or more File Service VM (= FSVM) is not working
and tries to remove and deploy a new File Service VM (= FSVM).
In the process of removing the bad File Service VM (= FSVM), the host side File Service Recovery Service might power it back. This will make the File Service VM (= FSVM) to be partially removed.

Resolution

This issue has been resolved by upgrading vCenter/ESXi to version 7.0 Update 1.

Workaround

Workaround to resolve this issue:

1.) Power off the File Service VM (= FSVM) that reported the Warning: "Virtual Machine Consolidation Needed Status"
2.) Right-click the VM and select "Delete from Disk" to remove the VM completely.
3.) The File Service Remediation process will deploy a new File Service VM (= FSVM) onto the same Host after Step 2 has been completed by the System.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
AGGL-7625：新規 Android アプリが Play ストア アプリに表示されない (79404)

KB
•
統合でのアップグレード/移行が正常に完了した後の外部 PSC の廃止 (75177)

KB
•
デバイス管理者機能から Android Enterprise への移行 (2960228)

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

KB
•
qlnativefc - 3.1.x を使用してホストを実行すると PSOD が発生する (79495)

Results 1-5 of 5

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere

Related Versions:

VMware vSphere 7.0.x

Take Our Survey

Support Assistant