Skip to content

Fix Redis/PostgreSQL connection in support bundle troubleshoot collectors#503

Open
saurya wants to merge 1 commit into
mainfrom
sv/redis-cache-error
Open

Fix Redis/PostgreSQL connection in support bundle troubleshoot collectors#503
saurya wants to merge 1 commit into
mainfrom
sv/redis-cache-error

Conversation

@saurya
Copy link
Copy Markdown
Contributor

@saurya saurya commented Mar 27, 2026

Summary

Fixes the Redis "no such host" error in Troubleshoot support bundle collectors.

Changes

  • Use FQDN for service URIs: Changed Redis and PostgreSQL URIs to use fully qualified domain names (.svc.cluster.local) to ensure DNS resolution works regardless of where the collector runs
  • Fix Redis secret reference: Use dynamic secret name from Values.redis.auth.existingSecret instead of hardcoded {{ .Release.Name }}-redis pattern
  • Bump chart versions: openhands 0.3.7, runtime-api 0.2.4

Details

The support bundle collector was failing with:

{"isConnected":false,"error":"dial tcp: lookup openhands-redis-master on ***:53: no such host"}

This was caused by:

  1. Using short service names without the full Kubernetes DNS suffix
  2. Redis secret name mismatch (the c2. Redis secret name mismatch (the c2. Redis secrol2. Redis secreking for openhands-redis)

Testing

  • Helm lint passes
  • Support bundle collection succeeds with Redis/Post- [ ] Support bundl checks

@saurya saurya force-pushed the sv/redis-cache-error branch from 09b3b16 to 6544e5f Compare March 27, 2026 18:13
- Use FQDN (.svc.cluster.local) for Redis and PostgreSQL URIs
- Fix secret references to use Values instead of hardcoded Release.Name patterns
- Bump chart versions: openhands 0.3.7, runtime-api 0.2.4

Co-authored-by: openhands <openhands@all-hands.dev>
@saurya saurya force-pushed the sv/redis-cache-error branch from 6544e5f to 3ab4cc2 Compare March 27, 2026 18:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant