| Summary: | stack traces in node logs | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Luke Meyer <lmeyer> |
| Component: | Node | Assignee: | Seth Jennings <sjenning> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Xiaoli Tian <xtian> |
| Severity: | low | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3.2.0 | CC: | aos-bugs, decarr, gblomqui, jokerman, mmccomas |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-07-03 15:21:25 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Luke Meyer
2016-10-12 21:02:39 UTC
I guess I should add some context that's filtered out here... each stack trace is actually a continuation of a log line such as this one: server.go:1100] GET /containerLogs/servicegateway-ofsprod/api-3-2do6k/api?follow=true&limitBytes=10485760&tailLines=1000: (9h11m52.950080139s) 400 I think all this is doing is logging a stack trace when there's an error condition, I'm not sure at what point. It's alarming to see in the logs though. Derek, sure, will look into it today. The stack trace is being logger for error http.StatusBadRequest(400, x190), and it is happening because ServeHTTP in pkg/kubelet/server/server.go sets a customer strack trace predictor than the default one used in pkg/httplog/log.go. Sent https://github.com/kubernetes/kubernetes/pull/35312 to kube upstream. Reducing severity, this will be picked up in a future rebase once Avesh's PR merges. Upstream PR merged 3 years ago |