Skip to content

Instantly share code, notes, and snippets.

@lamw

lamw/gist:0f04ac8cd9df35d42c9b8bd700ef9ece

Created October 21, 2022 11:23
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save lamw/0f04ac8cd9df35d42c9b8bd700ef9ece to your computer and use it in GitHub Desktop.
Save lamw/0f04ac8cd9df35d42c9b8bd700ef9ece to your computer and use it in GitHub Desktop.
Download ZIP
Query & Re-Enable vSphere Cluster Quick Start from VCDB
Raw
gistfile1.txt
# vSphere QuickStart can not be re-enabled after workflow has been Abandoned https://vdc-download.vmware.com/vmwb-repository/dcr-public/c476b64b-c93c-4b21-9d76-be14da0148f9/04ca12ad-59b9-4e1c-8232-fd3d4276e52c/SDK/vsphere-ws/docs/ReferenceGuide/vim.ClusterComputeResource.html#AbandonHciWorkflow
# QuickStart state is stored in 'hci_workflow_state' property which is not configurable outside of messing w/VCDB
# The following is NOT recommended but for information/learning purposes
# 1. Retrieve the ID value from your vSphere Cluster MoRef (e.g. domain-c84065)
# 2. Connect to VCDB
# Query vSphere Cluster for QuickStart state 'hci_workflow_state'
select * from vpx_hci_config_info where cluster_id = '84065';
# Re-enable QuickStart
update vpx_hci_config_info set hci_workflow_state = 'in_progress' where cluster_id = '84065';
# 3. Restart vmwawre-vpxd service
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment