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 %}

Related Blogs

 
thumbnail
FinOps Evolved: Key Insights from Day One of FinOps X Europe 2024

The FinOps Foundation’s flagship conference has kicked off in Europe, and it’s set to be a remarkable event. Attendees familiar…

 
thumbnail
FinOps for AI: Navigating the Wild West of Generative AI Costs

Buckle up, folks! The rapid evolution of cloud services and the rise of generative AI are reshaping how organizations approach…

 
thumbnail
Is Your FinOps Practice Ready for AI? Here’s How to Find Out

As a FinOps leader, you’re likely seeing the mad dash toward AI across industries—from automating workflows to cutting operational costs,…