How to remove a failed workflow in VMware Cloud Foundation
book
Article ID: 343400
calendar_today
Updated On:
Products
VMware Cloud Foundation
Issue/Introduction
This article provides steps to clean up a failed workflow in VMware Cloud Foundation
Note: In VMware Cloud Foundation 2.x there is a failed Workflow state in the SDDC Manager UI > Status > Workflows page. In VMware Cloud Foundation 3.x and 4.x there is a failed Workflow state in the Tasks list.
Environment
VMware Cloud Foundation 3.8.x VMware Cloud Foundation 2.x VMware Cloud Foundation 4.x VMware Cloud Foundation 3.9.x VMware Cloud Foundation 3.10.x
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:
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.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. There will be 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:
Note: Validate that the Workflow was deleted by re-issuing the command from Step 4. There should be an output stating "Node does not exist".
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.