User Request
Type: bug
Target: Console Application
Submitted by: @aashu2006
Console Request ID: c874479a-e1a4-423d-835e-f1903be63cd3
Description
What happened:
In pkg/agent/server_http.go:87, 97, 163, 172, and 250, errors that immediately return {"error": "internal server error"} to the caller are logged with slog.Warn. These are genuine failures not advisory notices — slog.Warn will be filtered out in error-severity log aggregators, hiding real cluster connectivity failures.
What I expected:
All five should use slog.Error since they result in HTTP 500 error responses to callers.
Steps to reproduce:
- Make Kubernetes nodes or events API unavailable
- Observe 500 responses but errors only appear at Warn level in logs
This issue was automatically created from the KubeStellar Console.
User Request
Type: bug
Target: Console Application
Submitted by: @aashu2006
Console Request ID: c874479a-e1a4-423d-835e-f1903be63cd3
Description
What happened:
In
pkg/agent/server_http.go:87,97,163,172, and250, errors that immediately return{"error": "internal server error"}to the caller are logged withslog.Warn. These are genuine failures not advisory notices —slog.Warnwill be filtered out in error-severity log aggregators, hiding real cluster connectivity failures.What I expected:
All five should use
slog.Errorsince they result in HTTP 500 error responses to callers.Steps to reproduce:
This issue was automatically created from the KubeStellar Console.