An 'Invalid configuration for device '0'' error is causing deployments to fail in Aria Automation
search cancel

An 'Invalid configuration for device '0'' error is causing deployments to fail in Aria Automation

book

Article ID: 404580

calendar_today

Updated On:

Products

VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

  • VM deployments fail in Aria Automation with an error message similar to:

Extensibility triggered task failed. Event ID: ########-####-####-####-############. Failure: Extensibility error received for topic compute.provision.post, eventId = '########-####-####-####-############': [10040] SubscriberID: ###-#######-################, RunnableID: ########-####-####-####-############ and SubscriptionID: sub_1655219897400 failed with the following error: Workflow run [########-####-####-####-############] completed with error [Task 'reconfigure' error: Invalid configuration for device '0'. (Dynamic Script Module name : vim3WaitTaskEnd#21)]

  • The same error occurs if you try to deploy the VM from the template directly within vCenter.

Environment

VMware Aria Automation 8.18.x

Cause

This issue may occur for one of the following reasons:

  • An invalid port group selected for a network card in the template.
  • Temporary disks, created during the cloning process, not being removed post-operation.
  • An ISO attached to the template's CD-ROM that no longer exists.

Resolution

To resolve the issue

  • Update the vCenter template: Modify or remove any unnecessary devices within the template.
  • Synchronize images for the Cloud Account/Region: Ensure your cloud account and region have the latest image configurations by initiating a synchronization.
  • Retry the deployment.

If the issue persists:

  • Create a new template in vCenter: Build a fresh template using the existing hard disks and the required configuration.
  • Synchronize images for the cloud account/region: Make sure your cloud account and region have the most up-to-date image configurations by running a sync.
  • Attempt the deployment again.