vCenter: Cluster Skip Quickstart Workflow via API


Summary:

Basically, whenever you reset vCenter, you might end up w/ a warning on a cluster running vSAN that's just annoying.  To circumvent, this from alerting, you need to disable quickstart.  Easy enough via UI, but API is a little weird here.

Details:

For one, code capture doesn't seem to understand this.  So no help there unfortunately.  Secondly, nothing named "quickstart" is in the API, so made this somewhat annoying to try and find.  Seems like someone had this question on the VMware communities forum 2 years ago w/ no answer.  Someone asked me internally, so I had to dig into it.

Basically, two things:

  1. You can create a cluster w/ quick start disabled from the get go by passing a false boolean to a parameter named: "InHciWorkflow" via API/PowerCLI call
  2. Secondly, to "skip QuickStart" on an already created cluster, you can call a method called:
    • "AbandonHciWorkflow"
So yeah, you can see how "quickstart" and "HCIWorkflow" SCREAM the same thing...

Code Sample:

Comments

Unknown said…
This is not working for me:

Exception calling "AbandonHciWorkflow" with "0" argument(s): "The operation is not allowed in the current state."
At line:1 char:1
+ $Cluster.ExtensionData.AbandonHciWorkflow()
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [], MethodInvocationException
+ FullyQualifiedErrorId : VimException

any ideas?
December 1, 2023 at 2:17 PM
Unknown said…
This is not working for me, any ideas?

Exception calling "AbandonHciWorkflow" with "0" argument(s): "The operation is not allowed in the current state."
At line:1 char:1
+ $Cluster.ExtensionData.AbandonHciWorkflow()
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [], MethodInvocationException
+ FullyQualifiedErrorId : VimException
December 1, 2023 at 2:18 PM
Zsoldier said…
It likely means that the quickstart is already disabled on the cluster. If you output $cluster.extensiondata.hciconfig, that'll give you an idea what state it's complaining about. 'invalid' workflow state means it's been skipped. If enabled, you should see something like in_progress.
December 1, 2023 at 2:40 PM
Unknown said…
This is what I get:

WorkflowState : done
DvsSetting : {VMware.Vim.ClusterComputeResourceDVSSetting}
ConfiguredHosts : {HostSystem-host-64858}
HostConfigProfile : VMware.Vim.ClusterComputeResourceHostConfigurationProfile
LinkedView :
December 1, 2023 at 3:07 PM
Unknown said…
WorkflowState : done
DvsSetting : {VMware.Vim.ClusterComputeResourceDVSSetting}
ConfiguredHosts : {HostSystem-host-64858}
HostConfigProfile : VMware.Vim.ClusterComputeResourceHostConfigurationProfile
LinkedView :
December 1, 2023 at 4:26 PM
Zsoldier said…
done seems to be equivalent to invalid. invalid being, "skipped", done likely means completed via traditional methods. https://vdc-repo.vmware.com/vmwb-repository/dcr-public/97e6db01-d441-472e-ad53-b48c2bb0e1e4/45347fb1-052d-44b7-b3e9-cbefc34488e3/SDK/vsphere-ws/docs/ReferenceGuide/vim.ClusterComputeResource.HCIWorkflowState.html

The error you get is because done is considered a 'terminal state'. Meaning abandonhciworkflow cannot change state from anything other than in_progress.
December 4, 2023 at 11:38 AM
Post a Comment

Popular posts from this blog

NSX-T: Release associated invalid node ID from certificate

Image
Summary: Basically had an expiring certificate registered in NSX-T that was associated to a node_id that is no longer valid.  Long story short, there wasn't anything obvious in API to delete or disassociate a certificate from a node_id for 3.2.2.  Not sure how things got in this state, but annotating for future reference.  This may change in future revisions, so always check API for latest. Details: Effectively had a stale node associated w/ a certificate that was expiring.  Could not delete certificate until that node was disassociated from the certificate. To get certificate details and associated node_id's, you can use the following curl call (UI works too): curl -k -X GET -H "Content-Type: application/json" -u admin https://<manager ip>/api/v1/trust-management/certificates/<cert UUID> Above will return something like this: Below must be run from one of the manager nodes via elevation to root: ONLY RUN THIS IF YOU ARE ABSOLUTELY SURE OF WHAT YOU ARE DO...
Read more

NSX-T: vCenter and NSX-T Inventory out of Sync (Hosts in vSphere not showing up in NSX-T)

Image
Summary: NSX-T loses synch w/ vCenter inventory, but statuses don't appear to show an issue.  Basically, you add a host to a vCenter cluster, NSX-T bits should start to automatically installing on new host.  Assuming you've created a Transport Node Profile and associated w/ the cluster.  The problem is that NSX-T doesn't see the new host and its link to the compute manager (vCenter) looks fine. Looks fine, Y U NO WORK!? So what's going on here?  This appears to affect NSX-T 2.5 and 2.5.1.  Cause is unknown. Workaround: Restart the cm-inventory service on each NSX-T mgmt/controller node using API or CLI. Details: If you were to query the status of the cm-inventory via API or CLI, you could query all 3 manager/controller nodes and get a status of running.  Even if the primary node associated w/ the VIP, if configured, is not necessarily in charge of inventory.  So you could restart the cm-inventory service till you are blue in the face ...
Read more

MacOS: AnyConnect VPN client was unable to successfully verify the IP forwarding table modifications.

Image
The VPN client was unable to successfully verify the IP forwarding table modification.  A VPN connection will not be established. Summary: I started running into issue utilizing Cisco AnyConnect on my Mac basically complaining about not able to overwrite IP forwarding tables.  This was on 4.6.x.  Since my VPN endpoints were not providing me w/ an updated client and w/ no access to Cisco Anyconnect downloads, my only option was to try openconnect.  It was totally worth it, here is why and how to set it up. PreReqs: Homebrew Installing OpenConnect: Launch MacOS Terminal brew install openconnect Getting VPN IP's/DNS Endpoints from AnyConnect: The information is typically located in your profile xml files located here: /opt/cisco/anyconnect/profile/somethingsomething.xml In the xml file, you are looking for "<HostAddress>typicallyaDNSName.com</HostAddress>" entry.  These are your VPN endpoints that you would need to pass to openconnec...
Read more