When upgrading Aria Automation 8.18.1 to VCFA 9.0, precheck fails with message - ”Unsupported cloud accounts of type NSX-V, NSX-T manager mode, or VCF with embedded NSX-T manager mode are present in the VCF Automation host"

Products

VCF Automation

Issue/Introduction

Unsupported cloud accounts of type NSX-V, NSX-T manager mode, or VCF with embedded NSX-T manager mode are present in the VCF Automation host.
Cannot upgrade Aria Automation 8.18.1 to VCF Automation 9.0.

Environment

Aria Automation 8.18.1
VCF Automation 9.0

Cause

This is applicable only if a VCF Cloud Account with embedded NSX-T is being flagged.
Under certain conditions, the precheck will falsely throw a warning related to NSX-T being in manager mode when it is actually in Policy mode.

Resolution

STEPS TO VERIFY ENDPOINT STATE

Verify that VCF cloud account associated with an NSX-T Policy endpoint was incorrectly flagged.

Find the cloud account id for VCF cloud account, it can be found from the url when accessing it via UI
Perform an API call to fetch the VCF cloud account
- GET - https://<vaa-url>/provisioning/uerp/provisioning/mgmt/endpoints/<vcf-cloud-account-id>
  NOTE: Please ignore first two character "2F" and copy rest of the ID and use it in <vcf-cloud-account-id>
  
  Check the payload for "endpointProperties" and see if the property "use.policy.api" is set and note it's value.
  If the property "use.policy.api" is set and it’s value is “true”, then this Release Note does not apply.
  Otherwise, proceed with next steps.
From the above payload copy the value from the custom property "nsx"
Perform an API call to fetch the NSX cloud accounts associated with VCF cloud account.
- GET - https://<vaa-url>/provisioning/uerp/<nsx-value>
  The response should have "endpointType" as "nsxt".
  If endpoint type is not set to "nsxt", please stop and contact Broadcom support.
- Check the payload for "endpointProperties" and see if the property "use.policy.api" is set and note it's value
If the value for property "use.policy.api" for "endpointType": "nsxt" is set to true, compare it with the property on VCF cloud account noted in Step 2. If the property is different or missing in either of API's(Step 2 and Step 4) then proceed with the steps to set this property on VCF cloud account to make these values consistent.
However, if the property "use.policy.api" for "endpointType": "nsxt" is not set or not set to "true". Do not proceed with the upgrade. The cloud account is using manager mode for NSX which is not supported in VCF 9.0 and will not work post upgrade.
Please refer the document on how to verify whether NSX-T is set to Manager mode or policy mode.

STEPS TO FIX PROPERTY IN DATABASE

The correction has to be applied against provisioning-db. Attached scripts will apply the required fix for the affected VCF cloud account(s). The script 'SimulateVCFCloudAccountsPolicyMode.sql' runs in 'simulate' mode, printing the results without making any updates to the database.
Once satisfied with the results, run the script ‘UpdateVCFCloudAccountsPolicyMode.sql’ to apply the changes to the database.

NOTE: Please take provisioning-db backup and snapshot of all Aria Automation nodes before executing the steps below.

Copy "SimulateVCFCloudAccountsPolicyMode.sql" to vRA appliance
SSH to vRA appliance
Execute the following command to list "postgres" pod(s)
- kubectl -n prelude get pods | grep postgres
Execute the following command to copy "SimulateVCFCloudAccountsPolicyMode.sql" file to postgres pod(s)
If there are multiple postgres pods, you need to copy "SimulateVCFCloudAccountsPolicyMode.sql" file to all postgres pods by replacing "postgres-0" in the command below with other postgres pod name, such as "postgres-1" and "postgres-2".
- kubectl -n prelude cp SimulateVCFCloudAccountsPolicyMode.sql postgres-0:SimulateVCFCloudAccountsPolicyMode.sql
  
  Note: Upon executing the above command you will see the following prompt "Defaulted container "control" out of: control, init (init)" this is an expected outcome.
Execute the following commands to change "SimulateVCFCloudAccountsPolicyMode.sql" file permission in postgres pod(s).
If there are multiple postgres pods, you need to replace "postgres-0" in the command with other postgres pod name, such as "postgres-1" and "postgres-2"
- kubectl -n prelude exec -it postgres-0 /bin/bash
  chmod 777 SimulateVCFCloudAccountsPolicyMode.sql
  exit
Execute the following command to start psql session:
- vracli dev psql provisioning-db
Once psql session is started, execute following command and check if "SimulateVCFCloudAccountsPolicyMode.sql" file is in responded file list.
- ! ls
  If file is not listed, please stop and contact Broadcom Support.

If "SimulateVCFCloudAccountsPolicyMode.sql" file is in the file list response from step 7, execute the following command to execute the script on provisioning-db.

\i SimulateVCFCloudAccountsPolicyMode.sql

Example output:

psql:SimulateVCFCloudAccountsPolicyMode.sql:22: NOTICE:  VCF cloud account found without use.policy.api property: <cloud-account-name>
psql:SimulateVCFCloudAccountsPolicyMode.sql:22: NOTICE:  Associated NSX found with use.policy.api set to true: <cloud-account-nsxt-fqdn>
DO

If satisfied with the results of the simulated run, repeat the above steps(Step 1 to Step 5 to copy the file "UpdateVCFCloudAccountsPolicyMode.sql") for “UpdateVCFCloudAccountsPolicyMode.sql” to apply the changes to the database, execute the following command to execute the script on provisioning-db.
- \i UpdateVCFCloudAccountsPolicyMode.sql
  
  Example output:
```
psql:UpdateVCFCloudAccountsPolicyMode.sql:25: NOTICE:  VCF cloud account found without use.policy.api property: <cloud-account-name>
psql:UpdateVCFCloudAccountsPolicyMode.sql:25: NOTICE:  Associated NSX found with use.policy.api set to true: <cloud-account-nsxt-fqdn>
psql:UpdateVCFCloudAccountsPolicyMode.sql:25: NOTICE:  Updating VCF property to match
DO
```

Attachments

SimulateVCFCloudAccountsPolicyMode.sql get_app

UpdateVCFCloudAccountsPolicyMode.sql get_app