zalando-incubator / zalando-incubator/stackset-controller
Remove confusing error message due to timeout/watch
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Go
- Stars
- 183
- Forks
- 29
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 5
Description
These error messages coming from glog, but we should delete these log entries, because the behaviour is intended and the client-go timeout works for WATCH, but not for all other API calls.
...
ERROR: logging before flag.Parse: E0808 14:07:03.579958 1 streamwatcher.go:109] Unable to decode an event from the watch stream: net/http: request canceled (Client.Timeout exceeded while reading body)
ERROR: logging before flag.Parse: E0808 14:07:33.581389 1 streamwatcher.go:109] Unable to decode an event from the watch stream: net/http: request canceled (Client.Timeout exceeded while reading body)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the WATCH timeout messages to streamwatcher.go:109 and inspect how client-go and glog produce them. Confirm whether the log entries originate in this controller or a dependency, then identify the relevant test or reproducible WATCH timeout behavior. Done means intended WATCH cancellations no longer emit these confusing error messages without changing other API-call timeout behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100