Bug 1804655
Summary: | Prometheus retention configuration get reset when minor upgrade is performed on OCP311 | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Daein Park <dapark> |
Component: | Monitoring | Assignee: | Sergiusz Urbaniak <surbania> |
Status: | CLOSED ERRATA | QA Contact: | Junqi Zhao <juzhao> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.11.0 | CC: | alegrand, anpicker, erooth, kakkoyun, lcosic, mirollin, mloibl, pkrupa, spasquie, surbania |
Target Milestone: | --- | Keywords: | Reopened |
Target Release: | 3.11.z | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
Cause:
If retention settings are configured, those are overwritten by ansible playbooks.
Consequence:
Prometheus retention configuration is not applied.
Fix:
Ansible now supports setting the retention configuration.
Result:
Prometheus retention configuration is applied.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2021-04-15 07:17:31 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
Daein Park
2020-02-19 10:52:42 UTC
openshift_cluster_monitoring_operator_prometheus_retention parameter is added Tested with # rpm -qa | grep ansible openshift-ansible-3.11.176-1.git.0.abb9886.el7.noarch ansible-2.6.20-1.el7ae.noarch openshift-ansible-playbooks-3.11.176-1.git.0.abb9886.el7.noarch openshift-ansible-docs-3.11.176-1.git.0.abb9886.el7.noarch openshift-ansible-roles-3.11.176-1.git.0.abb9886.el7.noarch set value for openshift_cluster_monitoring_operator_prometheus_retention and it takes affect, example: openshift_cluster_monitoring_operator_prometheus_retention=12h # oc -n openshift-monitoring get pod prometheus-k8s-0 -oyaml | grep -i "storage.tsdb.retention" - --storage.tsdb.retention=12h 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, 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-2020:0793 Hi team, I would like to re-open this BZ as i have an issue which i believe to be related. Please do advise if i need to create a new BZ. This pertains to the retention of the following Prometheus customisations. ~~~~ --storage.tsdb.retention=7d --storage.tsdb.min-block-duration=30m --storage.tsdb.max-block-duration=2h ~~~ AND nodeSelector: #node-role.kubernetes.io/infra: "true" infrarole: prometheus <<==There was a requirement to schedule to a dedicated node, post installation. Said changes were attempted first against statefulset.apps/prometheus-k8s AND then subsequently cm/cluster-monitoring-config when it became apparent that changes/cusomisations were lost. The CU upgraded from 3.11.286 to Upgrade 3.11.380 I note the creation of the variable openshift_cluster_monitoring_operator_prometheus_retention, but can you advise how best (if possible) to ensure the other customisations are retained. Many thanks |