User Request
Type: bug
Target: Console Application
Submitted by: @aashu2006
Console Request ID: d53c3530-e114-4114-9946-0aa045074093
Description
What happened:
In pkg/api/handlers/mcp_workloads.go:363-366, GetServices errors are silently dropped with a bare return and no errTracker.add() call. Unlike the pods and issues handlers which correctly track per-cluster errors, a failed cluster silently appears to have zero services with no error indication in the response.
What I expected:
Should use errTracker.add(clusterName, err) consistent with other multi-cluster handlers before returning.
Steps to reproduce:
- Make a cluster's service API unreachable
- Call the GetServices endpoint
- Observe the cluster shows zero services with no error indication
This issue was automatically created from the KubeStellar Console.
User Request
Type: bug
Target: Console Application
Submitted by: @aashu2006
Console Request ID: d53c3530-e114-4114-9946-0aa045074093
Description
What happened:
In
pkg/api/handlers/mcp_workloads.go:363-366,GetServiceserrors are silently dropped with a barereturnand noerrTracker.add()call. Unlike the pods and issues handlers which correctly track per-cluster errors, a failed cluster silently appears to have zero services with no error indication in the response.What I expected:
Should use
errTracker.add(clusterName, err)consistent with other multi-cluster handlers before returning.Steps to reproduce:
This issue was automatically created from the KubeStellar Console.