Bug 1997926
Summary: | container_runtime_crio_operations_latency_microseconds does not have quantile anymore | |||
---|---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Alan Chan <alchan> | |
Component: | Node | Assignee: | Sascha Grunert <sgrunert> | |
Node sub component: | CRI-O | QA Contact: | Weinan Liu <weinliu> | |
Status: | CLOSED ERRATA | Docs Contact: | ||
Severity: | low | |||
Priority: | low | CC: | aos-bugs | |
Version: | 4.8 | |||
Target Milestone: | --- | |||
Target Release: | 4.8.z | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | Doc Type: | No Doc Update | ||
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 2010831 2010841 (view as bug list) | Environment: | ||
Last Closed: | 2022-02-16 06:51:40 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: | 2010831, 2010841 |
Description
Alan Chan
2021-08-26 05:08:37 UTC
Sascha can you PTAL Confirmed, fix is incoming in https://github.com/cri-o/cri-o/pull/5258. I'll backport the fix if merged. Upstream PR merged, cherry-picking now. Upstream PR got merged into release-1.21 (https://github.com/cri-o/cri-o/pull/5266) Means that the next package build of CRI-O should contain the fix in 4.8. sh-4.4# oc get --raw /metrics --server http://${NODEIP}:9537 | grep "container_runtime_crio_operations_atency" | grep -c quantile 57 Verified to be fixed on $ oc get clusterversions NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.8.0-0.nightly-2022-02-09-031830 True False 43m Cluster version is 4.8.0-0.nightly-2022-02-09-031830 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 (OpenShift Container Platform 4.8.31 bug fix 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/RHBA-2022:0484 |