Error: "Service or view is not available for the selected object. Try again later. Should the issue continue please check the adapter Collection Status." error while accessing SDDC Manager in VCF Ops

Products

• VCF Operations

Issue/Introduction

• In VCF Ops UI under Build > Lifecycle > VCF Instances > Select VCF instance name, SDDC Manager details are not seen
• The adapter collection status is confirmed to be working normally.
• The /storage/log/vcops/log/web-vcf.log file confirms a certificate validation failure:

org.springframework.web.client.ResourceAccessException: I/O error on GET request for "https://<REDACTED_HOSTNAME>/plugin/metadata.json": Certificate for <<REDACTED_HOSTNAME>> doesn't match any of the subject alternative names: [<REDACTED_HOSTNAME>]
    at org.springframework.web.client.RestTemplate.createResourceAccessException(RestTemplate.java:926)
    at org.springframework.web.client.RestTemplate.doExecute(RestTemplate.java:906)

• Querying the local inventory API directly from the SDDC Manager appliance reveals it is incorrectly returning the shortname (<REDACTED_HOSTNAME>) in the hostName column, rather than the required Fully Qualified Domain Name (FQDN):

  curl http://localhost/inventory/sddcmanagercontrollers

         Output: 

 [ {"domainId":"", "vmName": "<REDACTED_HOSTNAME>", "ceipStatus": "ENABLED", "id":"", "status": "ACTIVE", "version":"9.1.0.0.25371088","hostName":"<REDACTED_HOSTNAME>"}]

       

Environment

VCF Ops:  9.1

Cause

• The SDDC Manager local inventory API is improperly configured to return the alias hostname of the appliance rather than the required Fully Qualified Domain Name (FQDN).
• This mismatch causes a certificate Subject Alternative Name (SAN) validation failure when VCF Operations attempts to securely communicate with the SDDC Manager API, thereby preventing the Lifecycle plugin from successfully registering and loading the view.

Resolution

Correct the vm_hostname value in the SDDC Manager's Platform database to reflect the full FQDN.

1. Take a snapshot without memory of the SDDC Manager VM from vCenter. See Take Snapshots of a Virtual Machine

2. Open an SSH session to the SDDC Manager appliance and elevate to root privileges using su.

3. Connect to the local PostgreSQL database:

   psql -U postgres -h localhost -d platform;

4. Query the controller table to view the current hostname value and record the corresponding id string:

   select * from sddc_manager_controller;

5. Retrieve the accurate FQDN (DNS name) for the SDDC Manager appliance as registered in your DNS/vCenter Server.

6. Update the database entry to the full FQDN using the id you recorded in step 3:

   update sddc_manager_controller set vm_hostname='<FQDN>' where id='<ID>';

7. Verify that the update was successful by querying the table again:

   select * from sddc_manager_controller;

8. Exit the PostgreSQL database prompt:

   exit;

9. Verify that the local API response now correctly reflects the full FQDN:

   curl http://localhost/inventory/sddcmanagercontrollers

10. Reboot the SDDC Manager appliance to apply the database changes and restore secure API communication with VCF Operations.

Additional Information

• Rebooting the SDDC Manger VM has resolved this issue in scenarious where the vm_hostname was already set to the FQDN