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

VMware Cloud Foundation Workload domain creation process fails on Enable Virtual SAN (55712)

Last Updated: 7/13/2018Categories: How toTotal Views: 2762Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

The Workload domain creation process fail on Enable Virtual SAN.

You see errors similar to the following in the /home/vrack/vrm/logs/vrack-vrm-debug.log on the SDDC Manager Controller VM:

2018-05-20 17:02:31.517 [pool-23-thread-8] DEBUG [com.vmware.vrack.vrm.workflow.tasks.vsan.EnableVsanTask] Failed to force provision.
2018-05-20 17:02:31.521 [pool-23-thread-8] WARN  [com.vmware.vrack.vrm.core.util.TimerUtil] Operation failed, retrying... 1
com.vmware.vrack.vrm.core.error.InternalServerErrorException: Failed to force provision for default policy.

​2018-05-21 19:18:29.251 [pool-23-thread-9] ERROR [com.vmware.vrack.vrm.workflow.tasks.AbstractVsanTask] vCenter: Enable Virtual SAN [EnableVsanTask]: failed. Cannot enable force provision
2018-05-21 19:18:29.251 [pool-23-thread-9] ERROR [com.vmware.vrack.vrm.core.engine.SimpleWorkflowEngine] Exception in task: vCenter: Enable Virtual SAN for Workflow 7b3f27fd-db30-49af-bbc6-d477e79566a6-0
com.vmware.vrack.vrm.workflow.tasks.TaskException: Cannot enable force provision

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Esxi Host summery tab shows warning message [ Host is in a vSAN Cluster but does not have vSAN service enabled].

The vSAN Network Health check  under "All hosts have a vSAN vmknic configured" will be showing that all the hosts in the cluster don't have vSAN vmknic presented.

The Esxi Hosts are not part of the vSAN cluster, and you can verify that by running the command on the Esxi hosts:-

esxcli vsan cluster get

For example:
[root@r1n10:~] esxcli vsan cluster get
vSAN Clustering is not enabled on this host

Examining the ESXi host participating in the vSAN cluster  you will find that they have a vSAN vmknic created and enabled for vSAN traffic.

The following steps can be used to  ensure if there is at least 1 vmknic enabled for vSAN traffic on the Esxi host:

From the vSphere Web Client:
- In vSAN 6.6 and later: Hosts and Clusters > ESXi host > Configure > Networking > VMkernel Adapters
- In vSAN 6.5 and earlier: Hosts and Clusters > ESXi host > Manage Networking > VMkernel Adapters

From the CLI use the following command:
​esxcli vsan network list

​For example:
VmkNic Name: vmk3
IP Protocol: IP
Interface UUID: 099e015b-122b-14c5-b258-246e968d1868
Agent Group Multicast Address: 224.2.3.4
Agent Group IPv6 Multicast Address: ff19::2:3:4
Agent Group Multicast Port: 23451
Master Group Multicast Address: 224.1.2.3
Master Group IPv6 Multicast Address: ff19::1:2:3
Master Group Multicast Port: 12345
Host Unicast Channel Bound Port: 12321
Multicast TTL: 5
Traffic Type: vsan

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Resolution

This is a known issue affecting VMware Cloud Foundation. There is currently no resolution

Workaround

You can workaround this issue by using the following steps:

Make sure that the Enabling vSAN workflow task is in a failed state.

Login to the  vCenter Web Client.

Browse on of the host in the vSphere Web Client navigator.

Right-click the host and select Maintenance Mode > Enter Maintenance Mode .

In the confirmation dialog that appears, clickYes.

(Note: Since the host is not part of vSAN cluster you won't be promoted to specify how vSAN will evacuate data)

Remove the host out of the Cluster level to the vRack-Datacenter level [Select the host icon in the inventory panel, and drag it to vRack-Datacenter]

Move the host back to the cluster.  [Select the host icon in the inventory panel, and drag it to the Cluster]

Right-click the host, and select Exit Maintenance Mode from the pop-up menu.

Esxi Host summery tab now will be showing warning message [Host cannot communicate with all other nodes in virtual SAN enabled cluster] instead of the [Host is in a vSAN Cluster but does not have vSAN service enabled].

Repeat steps 3-9 on  the other hosts in the cluster.

Login to the SDDC Manager UI and restart the Workload Domain Creation Workflow.

Notes:-

You will noticed that the "vCenter: Enable Virtual SAN" task status is SUCCESSFUL, and the creation workflow moved to "Virtual SAN: Claim Host Disks".

On the vCenter side you will noticed that DiskGroups are been created on the hosts.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

No results for undefined

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