Bug 1664862

Summary:	Configure openshift-monitoring without disabling cvo
Product:	OpenShift Container Platform	Reporter:	Alex Krzos <akrzos>
Component:	Monitoring	Assignee:	Frederic Branczyk <fbranczy>
Status:	CLOSED DUPLICATE	QA Contact:	Junqi Zhao <juzhao>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	4.1.0	CC:	aos-bugs, jeder, jokerman, minden, mmccomas, surbania
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	aos-scalability-40
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-02-04 16:30:24 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 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 ***