Error: "Service or view is not available for selected object" under Lifecycle Management after upgrading or importing vSphere 8.0 U3
search cancel

Error: "Service or view is not available for selected object" under Lifecycle Management after upgrading or importing vSphere 8.0 U3

book

Article ID: 456262

calendar_today

Updated On:

Products

VMware Cloud Foundation

Issue/Introduction

When navigating to Build > Lifecycle > VCF Instances in the VCF Operations UI, selecting a VCF Instance displays the following error message on the main panel:

"Service or view is not available for the selected object. Try again later in a couple of minutes."

 

VCF-Ops Log snippet " /storage/log/vcops/log/web-vcf.log ":

 

WARN web-vcf 24036 [ops@4413 threadId="547" threadName="plugin-discovery"] [com.vmware.vcf.operations.ui.vcenter.extensibility.discovery.VcenterPluginDiscovererImpl.warning] - Discovery failed for:
    source: ######-####-####-########
    source version: 9.1.1.0.25712839
    error: Failed to parse plugin source data

 WARN web-vcf 4012857 [ops@4413 threadId="219" threadName="plugin-discovery"] [com.vmware.vcf.operations.ui.vcenter.extensibility.discovery.VcenterPluginDiscovererImpl.warning] - Discovery failed for:
    source: ######-####-####-########
    source version: 9.1.1.0.25712839
    error: Failed to parse plugin source data

Environment

9.1.1

Cause

This issue occurs when stale session states or hung API threads within core SDDC Manager microservices prevent valid authentication token generation following the vSphere 8.0 U3 import/upgrade.

As a result, the VcenterPluginDiscovererImpl discovery service inside VCF Operations cannot authenticate or parse the plugin metadata returned from the target endpoints (Failed to parse plugin source data). This breaks the object tree binding for the instance in vcf-fleet-lcm, causing UI lifecycle rendering failures and disabling workload domain actions.

Resolution

To resolve this issue, execute the SDDC Manager service recovery script and force an inventory re-synchronization in VCF Operations:

 

1.Establish SSH Session to SDDC Manager:

 

SSH to the SDDC Manager appliance as the vcf user, then elevate to root:

su -

Note: Confirm the terminal prompt changes to root@<sddc-manager-hostname>.

 

2.Execute SDDC Manager Service Restart Script:

 

Run the automated service restart script to clear hung worker threads and reset internal microservice API sessions:

/opt/vmware/vcf/operationsmanager/scripts/cli/sddcmanager_restart_services.sh

Note: Allow 3 to 5 minutes for all core microservices to re-initialize completely.

 

3.Verify SDDC Manager System Health:

 

Check the system health endpoint via local API call to confirm all services are online:

curl -k https://localhost/api/v1/system/health

Note: Confirm the JSON response returns "status": "HEALTHY".

 

4.Trigger Inventory Sync in VCF Operations:
 
  1. Log into the VCF Operations web portal.

  2. Navigate to Administration > Integrations > VCF Adapter.

  3. Select your VCF instance and click Sync Inventory (or Start Collection).

  4. Clear your browser cache, log out, and log back in.

Note: Navigate to Build > Lifecycle > VCF Instances > [Your-Instance] and verify the lifecycle dashboard loads successfully and options like Add Workload Domain are active.