Supervisor is not appearing in VCFA with com.vmware.vapi.std error

Products

• VCF Automation

Issue/Introduction

• A healthy supervisor in vSphere is present in VCF Ops but not appearing in VCF Automation.
• Refreshing VC from VCFA gives the following error:
  
  com.vmware.vcloud.api.presentation.service.InternalServerErrorException: Internal Server Error:

Caused by: com.vmware.vapi.std.errors.InternalServerError: InternalServerError (com.vmware.vapi.std.errors.internal_server_error) => {
    messages = [LocalizableMessage (com.vmware.vapi.std.localizable_message) => {
    id = vapi.data.structure.union.extra,
    defaultMessage = Structure 'com.vmware.vcenter.namespace_management.supervisors.image_source_spec' has a union with a field 'library' not required for this case,
    args = [com.vmware.vcenter.namespace_management.supervisors.image_source_spec, library],
    params = <null>,
    localized = <null>
}, LocalizableMessage (com.vmware.vapi.std.localizable_message) => {
    id = vapi.bindings.typeconverter.struct.field.invalid,
    defaultMessage = Invalid field 'supervisor_image_source' in structure 'com.vmware.vcenter.namespace_management.clusters.info',
    args = [supervisor_image_source, com.vmware.vcenter.namespace_management.clusters.info],
    params = <null>,
    localized = <null>
}],

Environment

VCF Automation

Cause

The issue can occur when vSphere does not have access to the content library url: https://wp-content.broadcom.com

Resolution

To resolve the issue ensure the vCenter server hosting the supervisor has access to the url: https://wp-content.broadcom.com