Blog

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
The VMware Shakeup Hits Europe Differently: Sovereignty Isn’t a Preference, It’s a Constraint 

If you’re watching the hypervisor market shift from Europe, the conversation sounds different from what it does in North America.  Not because…

 
thumbnail
Why Cloud Resource Optimization Is Moving Beyond Recommendations

Cloud resource optimization has typically followed this pattern: teams identify inefficiencies, generate recommendations, review them, and apply changes where it feels safe to…

 
thumbnail
Making Kubernetes Optimization Safer, Smarter, and Easier to Scale 

Most teams don’t struggle to generate Kubernetes optimization recommendations. The harder part is acting on them in production without introducing risk, configuration…