Bug 1894677
Summary: | image-pruner job is panicking: klog stack | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Lalatendu Mohanty <lmohanty> |
Component: | Image Registry | Assignee: | Oleg Bulatov <obulatov> |
Status: | CLOSED ERRATA | QA Contact: | Wenjing Zheng <wzheng> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 4.6 | CC: | aos-bugs, sdodson, wking |
Target Milestone: | --- | Keywords: | Upgrades |
Target Release: | 4.7.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
Cause: the default log level for the pruner was 2
Consequence: when an error happened, the pruner was dumping stack trace
Fix: use the log level 1 by default
Result: only the error message is printed without stack traces
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2021-02-24 15:30:03 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: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1898152 |
Description
Lalatendu Mohanty
2020-11-04 18:42:34 UTC
Can you find in logs the line that starts with `panic: `? > Can you find in logs the line that starts with `panic: `? This is not a cluster we have direct access to. The panic stack is from an tarball uploaded from a customer cluster via Insights [1]. So the portion of the stack you see is all we have. I guess we could look in CI to see if we can find similar panics? Or get what we can from the stack-fragment to try to figure out a reproducer? Or get CCX to search their logs to see if we can find this still occurring somewhere where we can get the full logs (maybe in an OSD cluster?) or in a customer cluster where we can ask the customer for full logs. Or we can make the insights-operator smart enough to see panics and focus on the crashing goroutine. Lots of options, but nothing super easy. [1]: https://github.com/openshift/insights-operator/ Image pruner works well when upgrade with this path: 4.5.20->4.6.5->4.7.0-0.nightly-2020-11-18-203317. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2020:5633 |