Reply to Message

View discussion in a popup

Replying to:
Sasidhar1234
Enthusiast
Enthusiast

I figured out the issue is causing due to ${resource.hostname} given in the project under custom naming section.

Without network adapter the hostname was given as an input with ${resource.hostname} updated in project and the VM build was successful taking default VLAN.

As you suggested, tried from scratch without custom hostname and figured out the issue. Thanks for your help

Is there any way we can give custom hostname without any predefined configured input values(Env, OS flavor, Suffix number etc) with a network adapter in Blueprint design. My customer do not have a naming convention for hostname in place.

For ex: I want to build a VM name as "Titanic".