Bug 1664862 - Configure openshift-monitoring without disabling cvo
Summary: Configure openshift-monitoring without disabling cvo
Keywords:
Status: CLOSED DUPLICATE of bug 1666626
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Monitoring
Version: 4.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Frederic Branczyk
QA Contact: Junqi Zhao
URL:
Whiteboard: aos-scalability-40
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-01-09 21:14 UTC by Alex Krzos
Modified: 2019-03-12 14:27 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-02-04 16:30:24 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Alex Krzos 2019-01-09 21:14:13 UTC 
Description of problem:
In order to have node selectors configured in the openshift-monitoring cluster-monitoring-config configmap, I must disable the cvo or the changes will be reverted(in ~5 minutes or less).  Is there a way to create persisting changes to the openshift-monitoring configmap without disabling the cvo?

Version-Release number of selected component (if applicable):
4.0 - v0.9.0-master-12-g6880b3e44

How reproducible:
Always

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:


Currently I have to disable the CVO in order to allow me to configure openshift-monitoring

Disable CVO:
oc scale --replicas 0 -n openshift-cluster-version deployments/cluster-version-operator

Edit openshift-monitoring configmap
oc edit configmap cluster-monitoring-config -n openshift-monitoring
Comment 2 Frederic Branczyk 2019-02-04 16:30:24 UTC 
Closing this as a dupe of Bug 1666626 as that's been fixed and verified by QE.

*** This bug has been marked as a duplicate of bug 1666626 ***
Note You need to log in before you can comment on or make changes to this bug.