Bug 2021342
Summary: | Prometheus could not scrape fluentd for more than 10m | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Steven Walter <stwalter> |
Component: | Logging | Assignee: | Jeff Cantrill <jcantril> |
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Anping Li <anli> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 4.7 | CC: | amuller, anpicker, aos-bugs, arajkuma, erooth, periklis |
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: | 2021-11-17 17:56:06 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: |
Description
Steven Walter
2021-11-08 22:34:38 UTC
Other cluster operators(e.g. cluster-etcd-operator] defines explicit role[1] bindings[2] to the `prometheus-k8s` service account. You may need to follow the same. But I'm wondering why it was not done from cluster-logging operator! [1] https://github.com/openshift/cluster-etcd-operator/blob/master/manifests/0000_90_etcd-operator_01_prometheusrole.yaml [2] https://github.com/openshift/cluster-etcd-operator/blob/master/manifests/0000_90_etcd-operator_02_prometheusrolebinding.yaml It seems cluster-logging-operator has the necessary role[1] binding[2] to the `prometheus-k8s` service account. [1] https://github.com/openshift/cluster-logging-operator/blob/release-4.7/manifests/4.7/0100_clusterroles.yaml [2] https://github.com/openshift/cluster-logging-operator/blob/release-4.7/manifests/4.7/0110_clusterrolebindings.yaml The product OpenShift Logging does not compile any version 4.7. The last release bound to OCP is 4.6.z. Anything after that has a prefix 5.x (e.g. 5.0, 5.1, 5.2). If your image bundle registry is showing up anything like 4.7 it is a registry issue. Please use 5.x. Hi, my apologies, the OpenShift Logging version is: cluster-logging.5.2.2-21 It slipped my mind that the products are tracking different release cycles now. Can we re-open this against 5.2.2? Actually, looks like I set the version 4.7 when the component was set to Monitoring... Should we move this to JIRA as this is Logging 5.2? I know new bugs should be sent there but not sure what the protocol is if it's possibly related to other components like monitoring. Apologies for the comment spam; I'll close this and move to JIRA. |