Bug 1781948
Summary: | Ingress operator logs spurious "failed to sync ingresscontroller status" errors | |||
---|---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Miciah Dashiel Butler Masters <mmasters> | |
Component: | Networking | Assignee: | Miciah Dashiel Butler Masters <mmasters> | |
Networking sub component: | router | QA Contact: | Hongan Li <hongli> | |
Status: | CLOSED ERRATA | Docs Contact: | ||
Severity: | medium | |||
Priority: | unspecified | CC: | aos-bugs, dmace, mifiedle, mmasters, wabouham | |
Version: | 4.3.0 | |||
Target Milestone: | --- | |||
Target Release: | 4.4.0 | |||
Hardware: | x86_64 | |||
OS: | Linux | |||
Whiteboard: | ||||
Fixed In Version: | Doc Type: | Bug Fix | ||
Doc Text: |
Cause: The ingress operator was logging "failed to sync ingresscontroller status" errors and rapidly rerunning its synchronization loop when an ingresscontroller's "Degraded" status condition was true, even if the operator had in fact successfully updated the ingresscontroller's status.
Consequence: The ingress operator logs had spurious error messages.
Fix: The error handling logic was fixed to avoid the spurious error messages.
Result: The "failed to sync ingresscontroller status" errors should no longer appear in the ingress operator's logs when it updates an ingresscontroller's status.
|
Story Points: | --- | |
Clone Of: | 1781345 | |||
: | 1781950 (view as bug list) | Environment: | ||
Last Closed: | 2020-05-13 21:54:36 UTC | Type: | --- | |
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: | 1781950 |
Description
Miciah Dashiel Butler Masters
2019-12-10 23:21:03 UTC
verified with 4.4.0-0.nightly-2019-12-20-210709 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:0581 |