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 remove a failed workflow in VMware Cloud Foundation (51507)

Last Updated: 8/20/2021Categories: How toTotal Views: 9356Language:
English

2 like this article

Subscribe to get an email
newsletter with new updates

2 people found this helpful Please provide article feedback:

Purpose

This article provides steps to clean up a failed workflow in VMware Cloud Foundation

Note: In VMware Cloud Foundation 2.x you can view the failed Workflow state in the SDDC Manager UI >  Status > Workflows page. In VMware Cloud Foundation 3.x and 4.x you can view the failed Workflow state in the Tasks list.

Impact / Risks

Choosing the wrong workflow will lead to serious issues. Ensure the correct workflow ID is chosen and always have a backup/snapshot of the SDDC Manager Controller virtual machine.

Resolution

This is a known issue affecting VMware Cloud Foundation. Currently, there is no resolution.

Workaround

To workaround this issue in VMware Cloud Foundation 2.x:

Download ZooViewer from https://github.com/javaquery/zooviewer/releases/download/zooviewer-0.6/zooviewer-0.6.zip.

Disable the firewall by issuing this command:

systemctl stop ​iptables

Find the failed workflow ID in the SDDC Manager UI.

Click on the failed task's link after expanding the workflow on the status page.

Find the workflow ID in the browser URL.

Extract the contents of the zooviewer-0-6-bin.zip file.

Execute the zooviewer.bat file (windows, from command prompt as administrator or zooviewer.sh for linux) from the extracted files.

In the Enter the connection string window, enter the IP address

192.168.100.40:2181

Browse to /Workloads/Workflows in Zooviewer and select the workflow in question from step 3.

Verify if it is the correct workflow and click  Delete Node.

Enable the firewall by issuing this command:

systemctl start iptables

Note: It may take several minutes before the ZooKeeper data is fully populated.

To workaround this issue in VMware Cloud Foundation 3.x and 4.x:

Find the failed workflow ID in the SDDC Manager UI.

Expand the failed Workflow in the Tasks list and then click on the View Subtasks link.

Find the workflow ID in the browser URL. You will see something similar to: (monitoring-panel:monitoring/tasks/subtasks/c6db71f0-c64a-11e8-a84b-93b7cda0e148). c6db71f0-c64a-11e8-a84b-93b7cda0e148 is the Workflow ID.

Log in to the SDDC Manager VM as the vcf user and then issue su - to switch to the root user.

Issue a command similar to the following to delete the failed Workflow:

curl -X DELETE http://localhost/tasks/registrations/c6db71f0-c64a-11e8-a84b-93b7cda0e148

Note: Replace c6db71f0-c64a-11e8-a84b-93b7cda0e148 with the Workflow ID value obtained in Step 1b.

Related Information

Steps to delete a failed workflow in VMware Cloud Foundation 2.x from Zookeeper Using command line:-

Identify the failed workflow task ID.

login to the SDDC Manager Controller UI https://ipaddress:8443/vrm-ui

Click on Status >> Workflow Tasks >> Failed Tasks.

Click on the failed task >> The browser URL will show the failed Workflow ID.

SSH to the SDDC Manager Controller VM.

Run zkCli.sh to connect to zookeeper.

List the Workflows by issuing a command similar to the following:

ls /Workloads/Workflows/ed535779-9029-4186-9362-35535bda5373/--parameters

Run a command similar to the following to remove the failed workflow:

rmr /Workloads/Workflows/ed535779-9029-4186-9362-35535bda5373

Note: You can validate that the Workflow was deleted by re-issuing the command from Step 4. You should see output stating "Node does not exist".

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

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

KB
•
Download and Install VMware Fusion (2014097)

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 Cloud Foundation

Related Versions:

VMware Cloud Foundation 4.x

VMware Cloud Foundation 3.9.x

VMware Cloud Foundation 3.8.x

VMware Cloud Foundation 3.10.x

VMware Cloud Foundation 2.x

Take Our Survey

Support Assistant