Bug 1609056

Summary: [starter-ca-central-1] sdn pod error "Unable to get a bind address: failed to retrieve node IP:..."
Product: OpenShift Container Platform Reporter: Justin Pierce <jupierce>
Component: NodeAssignee: Seth Jennings <sjenning>
Status: CLOSED DUPLICATE QA Contact: DeShuai Ma <dma>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 3.10.0CC: aos-bugs, jokerman, mmccomas
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-07-30 20:48:15 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 Justin Pierce 2018-07-26 20:30:18 UTC
Description of problem:
One node's sdn pod in this cluster was in crash loop backoff with the following error:

F0726 19:44:26.231526   85471 network.go:100] Unable to get a bind address: failed to retrieve node IP: host IP unknown; known addresses: [{Hostname ip-172-31-27-114.ca-central-1.compute.internal}]

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

Additional info:
An IP issue which presented similarly was fixed recently in 3.9: https://bugzilla.redhat.com/show_bug.cgi?id=1601813 . Hoping this is the same problem and just has not landed in 3.10.14.

Comment 3 Seth Jennings 2018-07-30 20:48:15 UTC
https://github.com/openshift/ose/commit/0f1103b222705421380805acae4c56bb462e9b3f

First tag that includes this commit is v3.10.21-1

$ git tag --contains 0f1103b222705421380805acae4c56bb462e9b3f
v3.10.21-1
...

Duping to 3.10 bz 1603611 for above mentioned issue.

*** This bug has been marked as a duplicate of bug 1603611 ***