Attempting to deploy Identity Broker (vIDB) but vCenter (VCSA) is missing from dropdown menu.
search cancel

Attempting to deploy Identity Broker (vIDB) but vCenter (VCSA) is missing from dropdown menu.

book

Article ID: 419690

calendar_today

Updated On:

Products

VCF Operations

Issue/Introduction

Attempting to deploy Identity Broker (vIDB) via VCF Operations >> Fleet Management >> Lifecycle 

The desired vCenter is missing from Select vCenter Server dropdown menu on the Infrastructure tab as per the screenshot below:

 

 

The vCenter/VMware Cloud Foundation account has been added and has a green collection status via VCF Operations >> Administration >> Integrations >> Accounts

The desired vCenter is present as a Deployment Target via VCF Operations >> Fleet Management >> Lifecycle >> VCF Management >> Settings >> Deployment Targets

Environment

VCF Operations 9.0.1

Resolution

  1. Take a non-memory, non-quiesced snapshot of the Fleet Management appliance as per Take Snapshots of a Virtual Machine
  2. Access the Swagger API for Fleet Management and authorize as per How to Authorize VCF Operations Fleet Management API
  3. At the top of the Swagger page, ensure that the definition is set to public-api
  4. Expand the Data Center Controller section 
  5. Click on the following API call:

    GET /lcm​/lcops​/api​/v2​/datacenters​/{dataCenterVmid}​/vcenters

    Execute the above API call with dataCenterVmid set to DEFAULT_DC

  6. Examine the response, if the value for "sddcManagerHostname" is empty or set to null, then proceed with the following:

  7. Copy the entire response from the previous API call to a notepad.
  8. Click on the following API call:

    PUT ​/lcm​/lcops​/api​/v2​/datacenters​/{dataCenterVmid}​/vcenters​/{vCenterName}

    Execute the above API call with:

    dataCenterVmid
    to DEFAULT_DC
    vCenterName to vCenterName from previous API call response
    vCenterRequestDTO (body) : fill in the values using the previous API calls response as required and set the "sddcManagerHostname" to the correct, expected value.

  9. Execute the call, if all values are correct, the call will give a response code of 200.
  10. The vCenter will then be present in the dropdown menu and it will be possible to proceed with the vIDB deployment.