Bug 1891758
Summary: | the authentication operator may spam DeploymentUpdated event endlessly | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Standa Laznicka <slaznick> |
Component: | apiserver-auth | Assignee: | Standa Laznicka <slaznick> |
Status: | CLOSED ERRATA | QA Contact: | pmali |
Severity: | medium | Docs Contact: | |
Priority: | high | ||
Version: | 4.6 | CC: | aos-bugs, dahernan, mfojtik, pbertera, pmali |
Target Milestone: | --- | ||
Target Release: | 4.7.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
Cause:
A missed condition in authentication operator's code.
Consequence:
Authentication operator's log would get flooded with messages about an update to a deployment, even though no update happened.
Fix:
Ensure the deployment's generation is taken into account while deciding whether to update the operator's status.
Result:
The authentication operator's log should no longer receive messages about a deployment being updated when no such update occurs.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2021-02-24 15:28:28 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: | |||
Bug Depends On: | |||
Bug Blocks: | 1891795 |
Description
Standa Laznicka
2020-10-27 09:40:31 UTC
I can still see 5 events generated after single configuration change with the latest cluster version available today. $ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.7.0-0.nightly-2020-10-27-051128 True False 6h49m Cluster version is 4.7.0-0.nightly-2020-10-27-051128 I1109 10:37:02.362866 1 event.go:282] Event(v1.ObjectReference{Kind:"Deployment", Namespace:"openshift-authentication-operator", Name:"authentication-operator", UID:"3515d0fd-7e4b-4096-8502-1f048d06e472", APIVersion:"apps/v1", ResourceVersion:"", FieldPath:""}): type: 'Normal' reason: 'DeploymentUpdated' Updated Deployment.apps/oauth-openshift -n openshift-authentication because it changed I1109 10:37:05.560729 1 event.go:282] Event(v1.ObjectReference{Kind:"Deployment", Namespace:"openshift-authentication-operator", Name:"authentication-operator", UID:"3515d0fd-7e4b-4096-8502-1f048d06e472", APIVersion:"apps/v1", ResourceVersion:"", FieldPath:""}): type: 'Normal' reason: 'DeploymentUpdated' Updated Deployment.apps/oauth-openshift -n openshift-authentication because it changed I1109 10:37:08.760578 1 event.go:282] Event(v1.ObjectReference{Kind:"Deployment", Namespace:"openshift-authentication-operator", Name:"authentication-operator", UID:"3515d0fd-7e4b-4096-8502-1f048d06e472", APIVersion:"apps/v1", ResourceVersion:"", FieldPath:""}): type: 'Normal' reason: 'DeploymentUpdated' Updated Deployment.apps/oauth-openshift -n openshift-authentication because it changed I1109 10:37:14.963472 1 event.go:282] Event(v1.ObjectReference{Kind:"Deployment", Namespace:"openshift-authentication-operator", Name:"authentication-operator", UID:"3515d0fd-7e4b-4096-8502-1f048d06e472", APIVersion:"apps/v1", ResourceVersion:"", FieldPath:""}): type: 'Normal' reason: 'DeploymentUpdated' Updated Deployment.apps/oauth-openshift -n openshift-authentication because it changed I1109 10:37:18.160347 1 event.go:282] Event(v1.ObjectReference{Kind:"Deployment", Namespace:"openshift-authentication-operator", Name:"authentication-operator", UID:"3515d0fd-7e4b-4096-8502-1f048d06e472", APIVersion:"apps/v1", ResourceVersion:"", FieldPath:""}): type: 'Normal' reason: 'DeploymentUpdated' Updated Deployment.apps/oauth-openshift -n openshift-authentication because it changed Do these events continue indefinitely or are these all the events there are? It's perfectly natural to see _some_ of these in the authentication operator since it publishes them as it picks the configuration that might change from the moment the operator was started. The real question is - do you see them being posted in a loop even though no changes to the deployment are actually happening? Its not in loop and not even occurring when no changes to the deployment. As well, As per our discussion on slack. Marking as Verified. 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 (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement update), 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/RHSA-2020:5633 |