Blog

Custom Naming : Event Broker Subscriber error 10030

thumbnail

{% 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
VMWare Competitors: Exploring Migration Options after Broadcom’s Acquisition

As the saga of the recent $69 billion acquisition of VMware by Broadcom continues to play out, it has sent…

 
thumbnail
VMWare Alternatives – What’s Next For Your Cloud Practice

As a VMware partner, you may have received notice that Broadcom is terminating your contract.  It’s like the tech world’s…

 
thumbnail
Navigating the VMware Acquisition: A Pragmatic Approach to Migration in the Broadcom Era

Introduction: I received a text from a former colleague and friend out of the blue today that read “I guess…