Skip to content

fix: Handle cluster capacity fetch errors by returning detailed connection failure status #6912

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Ash-exp merged 1 commit into from
Jan 20, 2026
+6 −2
Merged

fix: Handle cluster capacity fetch errors by returning detailed connection failure status #6912

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 6 additions & 2 deletions pkg/overview/ClusterOverviewService.go
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -230,8 +230,12 @@ func (impl *ClusterOverviewServiceImpl) fetchClusterDataParallel(ctx context.Con
detail, err := impl.k8sCapacityService.GetClusterCapacityDetail(ctx, clusterCopy, false)
if err != nil {
impl.logger.Warnw("error fetching cluster capacity, skipping", "clusterId", clusterCopy.Id, "clusterName", clusterCopy.ClusterName, "err", err)
// Return error to skip this cluster
return nil, err
// Populate error for this cluster
detail = &capacityBean.ClusterCapacityDetail{
ErrorInConnection: err.Error(),
Status: capacityBean.ClusterStatusConnectionFailed,
}
// Continue to next cluster, returning error will stop the worker pool from further processing
}

// Set cluster metadata
Expand Down