VCF Automation Deployment Fails with Invalid Node Prefix

Products

• VCF Operations

Issue/Introduction

When the user triggers the Day-N API (`/v1/vcf-management-components`) to deploy VCF Operations management components with an invalid node prefix, the VCF Automation deployment fails with below error

[
  {
    "messageId": "LCMVSPHERECONFIG1000095",
    "message": "LCMVSPHERECONFIG1000095",
    "eventId": "#######-####-####-####-##########",
    "retry": true,
    "exceptionMessage": "Failed to create services platform cluster. Refer to /var/log/vrlcm/vmsp_bootstrap_####.log for more details. 
2025/03/20 08:42:40 ERROR : Invalid node prefix. vcfa-node- should be DNS/Kubernetes resource name compliant and must not be greater than 57 characters.\nERR:INIT0001 - Validating configuration\n",
    "exceptionStackTrace": "java.lang.Exception: Failed to create services platform cluster. Refer to /var/log/vrlcm/vmsp_bootstrap_xxxxx.log for more details. 2025/03/20 08:42:40 ERROR : Invalid node prefix. vcfa-node- should be DNS/Kubernetes resource name compliant and must not be greater than 57 characters.\nERR:INIT0001 - Validating configuration\n\n\tat com.vmware.vrealize.lcm.vmsp.plugin.tasks.BootstrapVMSPTask.execute(BootstrapVMSPTask.java:108)\n\tat com.vmware.vrealize.lcm.platform.automata.service.Task.retry(Task.java:158)\n\tat com.vmware.vrealize.lcm.automata.core.TaskThread.run(TaskThread.java:60)\n\tat java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)\n\tat java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)\n\tat java.base/java.lang.Thread.run(Unknown Source)\n",
    "localizedMessageId": "",
    "parameters": null
  }
]

The node prefix is a mandatory field during the VCF Automation (VCFA) deployment and must comply with the following requirements for successful deployment:

- It cannot be left blank.
- It must start and end with an alphanumeric character.
- It may only contain lowercase alphanumeric characters or hyphens.
- Its length must be less than 57 characters.

Environment

• VCF Automation 9.0
• VCF Operations 9.0
• Fleet Management 9.0

 

Cause

The failure occurs when an invalid node prefix is provided, which does not meet the specified conditions.

Resolution

To resolve the issue, follow the steps below to correct the node prefix:

1. Log in to VCF Operations.
2. Navigate to Fleet Management → Lifecycle.
3. Go to the Task section.
4. Click on the VCF Automation deployment failure task.
5. Select Retry to view all the fields available for update.
6. Update the Node Prefix with a valid value.
7. Click Submit to apply the changes.