Bug 2006290 - sdn emits events with garbage messages
Summary: sdn emits events with garbage messages
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.9
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.9.z
Assignee: Dan Winship
QA Contact: zhaozhanqi
Depends On: 2003859
TreeView+ depends on / blocked
Reported: 2021-09-21 12:08 UTC by Dan Winship
Modified: 2021-11-22 21:47 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 2003859
Last Closed: 2021-11-22 21:47:05 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift sdn pull 357 0 None open [release-4.9] Bug 2006290: Fix up event recorder usage (again) 2021-10-15 19:14:31 UTC
Red Hat Product Errata RHBA-2021:4712 0 None None None 2021-11-22 21:47:12 UTC

Comment 1 zhaozhanqi 2021-11-09 12:11:52 UTC

Verified this bug by cluster-bot launch openshift/sdn#357 aws

$ oc logs sdn-h7dqn -n openshift-sdn -c sdn | grep -i starting
I1109 11:03:01.274243    1648 cmd.go:159] Starting node networking (v0.0.0-alpha.0-392-g82ef950)
I1109 11:03:01.274257    1648 node.go:352] Starting openshift-sdn network plugin
I1109 11:03:01.532814    1648 healthcheck_ovs.go:18] Starting OVS health check
I1109 11:03:01.533328    1648 healthcheck_ovs.go:30] Starting SDN-OVS disconnection go-routine
I1109 11:03:01.777810    1648 node.go:401] Starting openshift-sdn pod manager
I1109 11:03:01.939589    1648 proxy.go:110] Starting multitenant SDN proxy endpoint filter
I1109 11:03:01.945490    1648 config.go:315] Starting service config controller
I1109 11:03:01.945496    1648 config.go:224] Starting endpoint slice config controller

Comment 6 errata-xmlrpc 2021-11-22 21:47:05 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 (OpenShift Container Platform 4.9.8 bug fix 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.


Note You need to log in before you can comment on or make changes to this bug.