Description of problem: custom setting in the logging-curator ConfigMap are overwritten during EFK stack upgrades (even though the changes seem to be initially detected and preserved by openshift_logging/library/logging_patch.py) Version-Release number of selected component (if applicable): $ rpm -q openshift-ansible openshift-ansible-3.11.219-1.git.0.8845382.el7.noarch How reproducible: always Steps to Reproduce: 1. oc -n openshift-logging edit cm logging-curator 2. Add a couple of custom `config.yaml` settings for specific projects: $ oc get cm logging-curator -n openshift-logging -o yaml | grep -v \# apiVersion: v1 data: actions.yaml: | config.yaml: | logging-project-1: delete: days: 30 logging-project-2: delete: days: 60 [...] curator5.yaml: [...] kind: ConfigMap [...] 3. Run the upgrade with `playbooks/openshift-logging/config.yml` Actual results: the `logging-project-X` retention settings are overwritten in the `logging-curator` ConfigMap during the EFK stack upgrade. Expected results: `logging-curator` ConfigMap custom settings to be preserved following an upgrade.
The PR wasn't merged into openshift-ansible-3.11.232-1.git.0.f0f2213.el7.noarch.
Verified on openshift-ansible-3.11.235
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:2990