Based on the pre-check validation you can change your input settings and rerun the pre-validation check in VMware Aria Suite Lifecycle.

How does pre-check validation work?

When you click the Run Pre-Check button, a report is generated indicating whether the pre-validation is in PASS or FAIL state. Therefore, based on the report you can modify your inputs given in the previous steps and click the RE - RUN PRE CHECK button. The report contains the following information:
  • Status of the Check
  • Check Name
  • Component/Resource against which the current check is run.
  • Result description about the check execution
  • Recommendation, if there is FAILURE or WARNING
The report also generates color coded status:
  • GREEN SYMBOL - PASSED
  • RED SYMBOL - FAILED
  • YELLOW SYMBOL - WARNING
  • GREEN FIXED SYMBOL - REMEDIATED & FIXED

You cannot proceed unless the pre-validation is successful. You can track the pre-validation request progress on the Request tab as the name VALIDATE_CREATE_ENVIRONMENT. When the pre-validation is finished and the NEXT button is activated, you can submit the request for deployment. When you are submitting, you can skip the pre-validation. By default, this flag is activated. This verifies pre-validations are run before deployment is started. If you skip this, then you can deselect the flag and click Submit. Pre-validation does not run again before the deployment begins.

If you click Submit with the pre-validation flag activated and a request named VALIDATE_AND_CREATE_ENVIRONMENT is created. If you click Submit by deselecting the pre-validation flag, a request named CREATE_ENVIRONMENT is created. You can track the progress of pre-validation requests in the VMware Aria Suite Lifecycle Request tab.

Before you run a pre-check on VMware Aria Automation, verify all the component VMs are communicating with VMware Aria Suite Lifecycle appliance. After you activate pre-check and submit the create environment, if pre-check fails then resume the wizard from the Request page with a request state as PRE_VALIDATION_FAILED. From the report, if the failure is due to the wrong IaaS credential then rerunning pre-check on updating the Windows password in the product details page still results in the wrong IaaS credential. To fix this, update the Windows password in the product details page at each node level and rerun the re-check.

If the VALIDATE_AND_CREATE_ENVIRONMENT request fails with a status PRE-VALIDATION-FAILED, then you can validate your inputs by clicking the icon under the action tab. This directs you to the wizard where you can modify your inputs and run PRE CHECK or click Submit for deployment. When deployment is complete, you can see the last run pre-validation report. This option is available from the environment page in the Manage Environments page. You can also view the last run report under View Last Pre Check Result under Environment.

Note: The VMware Aria Suite Lifecycle pre-check operation does not consider extended storage. If the extended storage option is used to deploy VMware Aria Operations nodes by using VMware Aria Suite Lifecycle, the pre-check might succeed but the deployment can fail due to insufficient disk space. For more information, see KB article 56365.

Only Automate checks is runs a manual pre-requisite for VMware Aria Suite in VMware Aria Suite Lifecycle. You can select DOWNLOAD SCRIPT and run on all the Windows machine. The zip contains a readme file, which explains how to run the script. This step is mandatory if you have selected VMware Aria Automation as one of the products during an environment creation.