Provisioning a machine with the same name as one that already exists can cause the existing machine to be deleted.
Article ID: 341911
Updated On:
Products
VCF Operations/Automation (formerly VMware Aria Suite)
Issue/Introduction
Symptoms:
When machines being provisioned using a strict naming convention encounter an existing machine with the same name, the provisioning fails (as expected) but the existing machine may be deleted as part of the clean up process.
When machines being provisioned using a strict naming convention encounter an existing machine with the same name, the provisioning fails (as expected) but the existing machine may be deleted as part of the clean up process.
Environment
VMware vRealize Automation 8.1.x
VMware vRealize Automation 8.2.x
VMware vRealize Automation 8.0.x
VMware vRealize Automation 8.2.x
VMware vRealize Automation 8.0.x
Cause
When a deployment fails, a clean up process occurs to roll back/ remove the provisioned resources. vRealize Automation mistakingly identifies the existing machine during that clean up and initiates a shutdown and delete of it.
Resolution
This issue is resolved in vRealize Automation 8.3 P1 and later.
To avoid this behavior in releases earlier than 8.3 P1, it is recommended to add incrementing numbers into your machine naming conventions to ensure unique names are generated for each provisioning task.
To avoid this behavior in releases earlier than 8.3 P1, it is recommended to add incrementing numbers into your machine naming conventions to ensure unique names are generated for each provisioning task.
Feedback
Yes
No
Powered by
