VCD Autoscale Plugin Job remains in Running state due to 'default' instance naming conflict

Products

• VMware Cloud Director

Issue/Introduction

VMware Cloud Director (VCD) Autoscale plugin jobs remain in a persistent "Running" state. API logs from the vcd-ext component show continuous retries failing with an Internal Server Error.

• Autoscale jobs do not transition to a terminal state.

• Stack trace originates from ValidateInstanceFromCli within vcd-ext.

Internal Server Error
 - ErrorMessage = {"level":"error","msg":"Instance 'default' already exist\n\nvcd-ext/cmd/instance/create.(*RealizeContext).ValidateInstanceFromCli\n\tvcd-ext/cmd/instance/create/validate.go:98\nvcd-ext/cmd/instance/create.(*RealizeContext).ValidateInstance\n\tvcd-ext/cmd/instance/create/validate.go:31\nvcd-ext/cmd/instance/create.(*RealizeContext).Realize\n\tvcd-ext/cmd/instance/create/realize.go:80\nvcd-ext/cmd/instance/create.(*Options).Run\n\tvcd-ext/cmd/instance/create/cmd.go:131\nvcd-ext/cmd/instance/create.NewCreateCommand.func2\n\tvcd-ext/cmd/instance/create/cmd.go:36\ngithub.com/spf13/cobra.(*Command).execute\n\tgithub.com/spf13/[email protected]/command.go:872\ngithub.com/spf13/cobra.(*Command).ExecuteC\n\tgithub.com/spf13/[email protected]/command.go:990\ngithub.com/spf13/cobra.(*Command).Execute\n\tgithub.com/spf13/[email protected]/command.go:918\nvcd-ext/cmd/cli.Run\n\tvcd-ext/cmd/cli/cli.go:58\nmain.main\n\t/opt/src/vcd-ext/main.go:13\n"}
,Log=(API Access) https://example.com/cloudapi/1.0.0/entities/urn:vcloud:entity:vmware:solutions_add_on_instance:xxxx-xxxx/behaviors/urn:vcloud:behavior-interface:invoke:vmware:solutions_add_on_instance:1.0.0/invocations/xxxx-xxxx/log

 com.vmware.vcloud.api.presentation.service.InternalServerErrorException: Internal Server Error
    at com.vmware.vcloud.common.future.FutureUtil.convertExecutionException(FutureUtil.java:233)
    at com.vmware.vcloud.common.future.FutureUtil.checkCompletedFuture(FutureUtil.java:194)
    at com.vmware.vcloud.behaviors.execution.impl.BehaviorExecutionActivity$NotificationPhase.invoke(BehaviorExecutionActivity.java:151)
    at com.vmware.vcloud.activity.executors.ActivityRunner.runPhase(ActivityRunner.java:175)
    at com.vmware.vcloud.activity.executors.ActivityRunner.run(ActivityRunner.java:112)
    at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
    at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
    at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
    at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
    at java.base/java.lang.Thread.run(Thread.java:829)
Caused by: java.lang.IllegalStateException: ErrorMessage = {"level":"error","msg":"Instance 'default' already exist\n\nvcd-ext/cmd/instance/create.(*RealizeContext).ValidateInstanceFromCli\n\tvcd-ext/cmd/instance/create/validate.go:98\nvcd-ext/cmd/instance/create.

Environment

10.x

Cause

• A naming conflict occurs during the instance realization phase.
• The vcd-ext CLI validation logic detects that an instance named 'default' already exists, triggering an Internal Server Error and subsequent automated retries.

Resolution

• Allow Retry Exhaustion: Let the automated retry mechanism reach its configured limit or timeout period. The job will terminate automatically once the threshold is met.
• Instance Validation: Verify the existing instances in the VCD environment to ensure no duplicate 'default' identifiers exist that conflict with the autoscale plugin configuration.
• Configuration Audit: Update the autoscale plugin configuration to use unique naming conventions or ensure the 'default' instance is not being redundantly targeted for creation.