New: StormForge GPU optimization is now in early access Get started today close-btn
Blogs

Custom Naming : Event Broker Subscriber error 10030

{% raw %}

Problem Description:

The Custom Naming machineRequested workflow runs for a long time and eventually fails with this error:

 

Event Broker Subscriber error 10030 – {‘com.vmware.csp.core.designer.service@event.subscription.workflow.execution.timeout}

 

Cause:

The Hostname being generated only contains the sequence number and no other characters. This is caused when none of the templated values expected in the Naming Standard are set or are null.

 

 

For example:

The Custom Naming Standard template looks like this:

    {{naming.OS}}{{{naming.Environment}}{{naming.AppType}}{{sequence.seqProfile}}

If the values for properties for naming.OS, naming.Environment and naming.AppType are not provided, you end up with a Hostname that consists only of the sequence number, e.g. 001.  This is not a valid hostname, and the workflow keeps looping and eventually times out.  These values are typically set using vRA property definitions where the requestor selects the value from a dropdown menu, or they could be set on other elements in vRA, such as in the Custom Properties on things like Reservations, Business Groups, Endpoints, etc.

 

Resolution:

Make sure to set all properties expected in your Custom Naming Standard and Naming Sequence profiles. {% endraw %}

Sign up for our newsletter

Exclusive insights and strategies for cloud pros. Delivered straight to your inbox.


AUTHOR
Patrick Campbell
  Learn more

Related Blogs

 
thumbnail
Bringing Neoclouds to the Enterprise

Back in July, Yasmin, our COO, wrote about Meta renting out its spare GPU capacity. Since then, neoclouds have kept…

 
thumbnail
What is Cloud Automation and Orchestration?

Cloud automation is the use of software, scripts, and workflows to complete individual tasks in a cloud environment, like provisioning…

 
thumbnail
AI Agent Governance – Five Questions to Ask

Infrastructure teams are already running AI agents against their cloud and on-prem environments. For every change an agent makes, teams…