Description of problem: 'complete' word seems to be wrongly spelled $ oc logs sdn-8jc9d | grep -i comlete I0515 02:10:27.979968 1732 cmd.go:223] openshift-sdn network plugin waiting for proxy startup to comlete Version-Release number of selected component (if applicable): 4.1.0-0.nightly-2019-05-09-204138 How reproducible: Always Steps to Reproduce: 1.Check sdn logs on cluster under openshift-sdn namespace Actual results: I0515 02:10:27.979968 1732 cmd.go:223] openshift-sdn network plugin waiting for proxy startup to comlete Expected results:I0515 02:10:27.979968 1732 cmd.go:223] openshift-sdn network plugin waiting for proxy startup to complete Additional info:
https://github.com/openshift/origin/pull/23280
Dan, if you manually associate a PR with a Bugzilla, you need to promote to MODIFIED when the PR lands so ART can sweep it into an errata when they build a nightly and move it to ON_QA for QE to verify the fix. Easiest way to do that is with the Bugzilla bot in GitHub and a 'Bug 1710652: ' prefix on your PR subject. Catching up now, this landed [1], and 4.2.0-rc.1 has it: ose$ oc adm release info --commits quay.io/openshift-release-dev/ocp-release:4.2.0-rc.1 | grep hyperkube hyperkube https://github.com/openshift/ose 463c73f1f71e1f532cf4d8310676ea94bf42c8b6 ose$ git log --oneline 463c73f1f71e1f532cf4d8310676ea94bf42c8b6 | grep 73594bd 73594bd365 Merge pull request #23280 from dcbw/sdn-log-spelling-fix Unfortunately we have no 463c73f1f71e1f532cf4d8310676ea94bf42c8b6 in origin, but that's bug 1711135. Moving to MODIFIED so ART can sweep this up. [1]: https://github.com/openshift/origin/pull/23280#event-2442090668
Verified on build:4.2.0-0.nightly-2019-10-07-203748 huiran-mac:script hrwang$ oc logs sdn-dgw5k -n openshift-sdn| grep -i comlete huiran-mac:script hrwang$ oc logs sdn-dgw5k -n openshift-sdn| grep -i "openshift-sdn network plugin waiting" I1008 02:26:17.855621 1902 cmd.go:171] openshift-sdn network plugin waiting for proxy startup to complete
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-2019:2922