Stale upgrade plan entities on VCF Operations 9.1 after component cleanup

Products

• VCF Operations

Issue/Introduction

• Viewing the upgrade plan in VCF Operations 9.1 UI (Build > Lifecycle > VCF Management > Upgrade) displays stale entries with missing "Component" and "Location" details.

• The source version of the upgrade is listed as undefined.

• Selecting the stale record checkbox in VCF Operations 9.1 UI and attempting to Run Precheck or Reconfigure fails with the following error:

  Failed to run action on component. Upgrade plan validation failed. The following validation errors were detected: VCF_LCM_FLEET_UPGRADE_400_INVALID_UPGRADE_PLAN_SPEC. Review the validation errors X and correct the input data. Ensure all component IDs in the filter exist in the upgrade plan inventory. Verify that all required fields are provided and have valid values.
  

• The respective task logs from the vcf fleet build pod (kubectl logs -n vcf-sddc-lcm vcf-sddc-build-service-sddcbuild-###############) entries similar to :
  ERROR sddc-build-service <appi and logger details>
Failed to authenticate OkHttp request GET https://<VCFops-fqdn>/api/vl/components/<component-id>: <component-fqdn>: Name or service not known

ERROR sddc-build-service <API and logger details>- Request failed after 6ms: GET https://<VCFops-fqdn>/api/vl/components/<component-id>: <component-fqdn>:
java. net . UnknownHostException: <component-fqdn>: Name or service not known
at java. base/java. net. Inet6AddressImpl. lookupAllHostAddr (Native Method)
at java. base/java. net . Inet6AddressImpl . lookupAllHostAddr (Unknown Source)
at java.base/java.net. InetAddress$PlatformResolver. lookupByName (Unknown Source)
at java.base/java.net. InetAddress. getAddressesFromNameService (Unknown Source)
...
Caused by: java.net.UnknownHostException: <component-fqdn>: Name or service not known

Environment

• VCF operations 9.1

Cause

• The associated components were deleted / cleaned up from VCF Operations using cleanup_component.py from KB441333.
• The cleanup task failed to clean up records on the upgrade planner, thus leaving them stale with no valid component references. 

Resolution

• This requires database investigation, isolation and modification to remove the stale references. Thus, we recommend reaching out to Broadcom Support referencing the KB454012.