Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1819227

Summary: WMCO is unnecessarily watching pods
Product: OpenShift Container Platform Reporter: Sebastian Soto <ssoto>
Component: Windows ContainersAssignee: vhire <vhire>
Status: CLOSED ERRATA QA Contact: gaoshang <sgao>
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: aos-bugs, gmarkley, rgudimet
Target Milestone: ---   
Target Release: 4.5.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: 2020-07-13 17:24:11 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 Sebastian Soto 2020-03-31 13:59:11 UTC
Description of problem:
The WMCO is watching pods when it does not need to
https://github.com/openshift/windows-machine-config-operator/blob/master/pkg/controller/windowsmachineconfig/windowsmachineconfig_controller.go#L76

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
Run the operator

Actual results:
WMCO is watching pods

Expected results:
WMCO does not watch pods. WMCO works without having RBAC permissions to watch pods.

Additional info:

Comment 3 gaoshang 2020-05-20 09:35:17 UTC
QE verification is blocked by Bug 1837936, will verify it when problem resolved,thanks.

Comment 4 gaoshang 2020-05-28 17:58:39 UTC
QE testing passed

Version:
windows-machine-config-operator git commit: 8edef3c68c34c7c558cf3f039c9eb8706f429d7c

Steps:

After removed watch pods and RBAC permissions to watch pods, wmco works as expected

Comment 6 errata-xmlrpc 2020-07-13 17:24:11 UTC
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:2409