Bug 1501850

Summary: Networkpolicy plugin checks pod status too fast that there are lots of warnings about PodIP is not set in node log
Product: OpenShift Container Platform Reporter: Meng Bo <bmeng>
Component: NetworkingAssignee: Dan Winship <danw>
Status: CLOSED ERRATA QA Contact: Meng Bo <bmeng>
Severity: low Docs Contact:
Priority: medium    
Version: 3.7.0CC: aos-bugs, danw, jeder
Target Milestone: ---   
Target Release: 3.7.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Cause: OpenShift was treating a non-error situation as an error Consequence: Multiple error messages of the form "PodIP is not set for pod ..." might be logged on a node each time a new pod started, when using the networkpolicy plugin. (The actual functioning of NetworkPolicy was not affected; the bug is solely that spurious messages were logged.) Fix: The message is now logged at a lower level. Result: Clusters with standard --loglevel values will no longer see this message.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2017-11-28 22:17:21 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 Meng Bo 2017-10-13 10:41:29 UTC 
Description of problem:
Try to create pod with network policy plugin env, there are lots of warnings about podip is not set in node log.

Oct 13 18:00:05 ose-node2.bmeng.local atomic-openshift-node[28733]: W1013 18:00:05.042864   28733 networkpolicy.go:451] PodIP is not set for pod "u1p1/test-rc-rx7xd"
Oct 13 18:00:05 ose-node2.bmeng.local atomic-openshift-node[28733]: W1013 18:00:05.089130   28733 networkpolicy.go:451] PodIP is not set for pod "u1p1/test-rc-rx7xd"
Oct 13 18:00:05 ose-node2.bmeng.local atomic-openshift-node[28733]: W1013 18:00:05.140096   28733 networkpolicy.go:451] PodIP is not set for pod "u1p1/test-rc-rx7xd"
Oct 13 18:00:05 ose-node2.bmeng.local atomic-openshift-node[28733]: W1013 18:00:05.154872   28733 networkpolicy.go:451] PodIP is not set for pod "u1p1/test-rc-8zb30"
Oct 13 18:00:05 ose-node2.bmeng.local atomic-openshift-node[28733]: W1013 18:00:05.166079   28733 networkpolicy.go:451] PodIP is not set for pod "u1p1/test-rc-8zb30"
Oct 13 18:00:05 ose-node2.bmeng.local atomic-openshift-node[28733]: W1013 18:00:05.248377   28733 networkpolicy.go:451] PodIP is not set for pod "u1p1/test-rc-8zb30"


Version-Release number of selected component (if applicable):
v3.7.0-0.150.0

How reproducible:
always

Steps to Reproduce:
1. Setup multi node env with network policy plugin
2. Try to create pod on the env
3. Check the node log during the pod creation

Actual results:
There are lots of warnings about the podip is not set.


Expected results:
To avoid the warning, we should either check the pod status later when the pod is already running or reduce the frequency if we have to check before pod running.


Additional info:
Comment 1 Dan Winship 2017-10-18 16:58:04 UTC 
https://github.com/openshift/origin/pull/16933
Comment 3 Meng Bo 2017-11-03 03:28:44 UTC 
Tested on ocp build v3.7.0-0.190.0
The message will not be shown under loglevel 2 and will not be shown as wanring.
Comment 6 errata-xmlrpc 2017-11-28 22:17:21 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/RHSA-2017:3188