Error "Services are not available for this namespace" in VCF Automation 9.1

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

• VCF Automation 9.1 fails to display namespaced resources in the Services view. When navigating to the affected namespace, the UI presents the following error: "Services are not available for this namespace, try again later or check with your administrator."
  
  
• Users are unable to view or manage resources within specific namespaces in the VCF Automation tenant portal.
  
  
• The Tenant Manager service logs (/var/log/services-logs/prelude/tenant-manager-0/file-logs/vcloud-container-debug.log) show explicit authentication failures and connection timeouts:
  
  

  ERROR | auto-pool-caffeine-cache-pool-36-thread-#### | c.v.v.w.c.WcpAuthenticationRestTemplate | Failed to authenticate with wcp ip #### | org.springframework.web.client.ResourceAccessException: I/O error on POST request for "https://####:443/wcp/login": Connect to https://####:443 failed: Connect timed out
  
  

  or
  
  Connection time out messages trying to reach Kubernetes API server
  
  

  ERROR Backend-activity-pool-#### | c.v.s.b.s. SupervisorWatchJobSCreateWatcherActivity
  | [Activity Execution] Failed watching on events, vc- id=a#######-####-#####-########-##### control-plane-ip ###.###.###.###, type-STORAGE_POLICY_QUOTAS, job-id=####-#######-######-##### - ,
  Current Phase: SupervisorWatchJob$CreateWatcherActivitysCreateWatchPhase|ACTIVITY_HANDLE=activity=com.vmware.ssdc.backend.services.SupervisorWatchJobSCreateWatcherActivity,urn:uuid:####-######-######-#####-#####)
  java.lang. IllegalStateException: java.net.SocketTimeoutException: Connect timed out
  at com.vmware.vcf.backend.kubernetes.watcher.CustomKubernetesGenericApi.executeList(CustomKubernetesGenericApi.java:160)

Environment

• VMware Cloud Foundation 9.1
• VCF Automation 9.1
• vSphere Supervisor Cluster

Cause

VCF Automation appliance nodes are unable to establish network connectivity to the vSphere Supervisor cluster API endpoint. This occurs when TCP traffic on required outbound communication ports—specifically port 443 (WCP authentication) and port 6443 (Kubernetes API server)—is blocked by a network firewall or routing restriction between the VCF Automation appliance network and the Supervisor cluster management network.

Resolution

To resolve this issue, bidirectional network connectivity must be restored between the VCF Automation appliance nodes and the vSphere Supervisor cluster management network.

1. Log in to the VCF Automation appliance via SSH.
   
   
2. Test connectivity from the VCF Automation runtime container to the Supervisor cluster IP on port 443:
   
   

   curl -v telnet://<Supervisor_Cluster_IP>:443
   
   curl -v telnet://<Supervisor_Cluster_IP>:6443
   

    

3. If the connection fails with a Connection timed out, reconfigure network firewall rules, access control lists (ACLs), or routing tables to allow outbound TCP traffic on the following ports from all VCF Automation appliance node IPs to the Supervisor cluster control plane endpoint:
   • • Port 443: HTTPS / WCP Login
     • Port 6443: Kubernetes API
4. Once the ports are opened, verify the connection again using the curl command from Step 2.
   
   
5. Refresh the VCF Automation UI and confirm that namespaced resources are visible in the Services view.

Additional Information

For a comprehensive list of port specifications and communication requirements for VMware Cloud Foundation components, refer to the VMware Ports and Protocols tool.

To stay updated on fix status for related defects, subscribe to this article (see https://knowledge.broadcom.com/external/article/275360).