Bug 1731885

Summary:	Cluster operator machine-config is reporting a failure when proxy enabled
Product:	OpenShift Container Platform	Reporter:	Gaoyun Pei <gpei>
Component:	Installer	Assignee:	Abhinav Dahiya <adahiya>
Installer sub component:	openshift-installer	QA Contact:	Gaoyun Pei <gpei>
Status:	CLOSED DEFERRED	Docs Contact:
Severity:	high
Priority:	high	CC:	amurdaca, dhansen, hongli, juzhao, wewang, wzheng
Version:	4.2.0	Keywords:	Reopened
Target Milestone:	---
Target Release:	4.2.0
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:	2019-08-13 20:14:34 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:

Comment 7 Daneyon Hansen 2019-07-23 22:56:19 UTC

This is the WIP PR for adding a proxy controller to the cluster-network-operator: https://github.com/openshift/cluster-network-operator/pull/245

Comment 8 Daneyon Hansen 2019-07-30 15:44:15 UTC

Can you review the MCO logs and see if it is reconciling the Proxy? My understanding is that when when a proxy changes, such as this case, MCO needs to restart (rolling) the nodes for the proxy changes to take effect.

Comment 9 Antonio Murdaca 2019-07-30 15:50:18 UTC

I should start a rollout yeah, the MCO has the proxy informer configured here https://github.com/openshift/machine-config-operator/pull/901/files#diff-554de5523753fda8c93e7008c9bd947fR162

Comment 11 Antonio Murdaca 2019-08-06 10:19:59 UTC

alrighty, so MCO is re-rolling just fine.

Comment 12 Abhinav Dahiya 2019-08-13 20:14:34 UTC

(In reply to Antonio Murdaca from comment #11)
> alrighty, so MCO is re-rolling just fine.

closing