Upgrade to vRA 8.7 and above fails with Exception Error Code "LCMVRAVACONFIG90030"
book
Article ID: 318264
calendar_today
Updated On:
Products
VMware Aria Suite
Issue/Introduction
Symptoms:
- Upgrade from 8.7 and above fails with the error:
Error while deploying infrastructure and application services
- LCM shows the error code LCMVRAVACONFIG90030
- viDM configuration in vRA missing the defaultOrgName by running the command vracli vidm
For example:
"clients": {
"ClientID": "prelude-aSR79QWc2W",
"ClientIDUser": "prelude-user-Q4AsOcQNCx",
"ClientSecret": "SHog9ZdiIG",
"ClientSecretUser": "bZk66FYWKf"
},
"defaultOrgAlias": "",
"isDefaultOrgAliasUpdated": true,
"sha256": "<sha256_fingerprint>",
"url": "https://vidm_url",
"user": "configadmin",
Environment
VMware vRealize Automation 8.x
Cause
This issue is caused by missing defaultOrgName in vIDM configuration if vRA was initially installed 8.2 or earlier version.
Resolution
Known issue with all VRA's that were initially installed 8.2 or earlier versions and trying an upgrade to 8.7 and above.
Workaround:
To workaround this issue, set the missing defaultOrgName by reapplying vIDM configuration.
- If you already tried to upgrade and it failed, revert back to the snapshot
- Open an SSH to vRA appliance
- Run the command to check the current VIDM configuration:
vracli vidm
Note: The output should be missing the defaultOrgName field.
- Run the below command:
vracli vidm set <URL of vIDM> <vIDM Admin> <vRA configuration admin>
For example:
vracli vidm set https://vidm-node.local admin configadmin
Note: You will be prompted to enter password for vIDM.
- Apply vIDM configuration:
vracli vidm apply
- Start vRA services again:
/opt/scripts/deploy.sh
- Retry the upgrade.
Feedback
thumb_up
Yes
thumb_down
No