Bug 1609056 - [starter-ca-central-1] sdn pod error "Unable to get a bind address: failed to retrieve node IP:..."
Summary: [starter-ca-central-1] sdn pod error "Unable to get a bind address: failed to...
Status: CLOSED DUPLICATE of bug 1603611
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Node
Version: 3.10.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: ---
Assignee: Seth Jennings
QA Contact: DeShuai Ma
Depends On:
TreeView+ depends on / blocked
Reported: 2018-07-26 20:30 UTC by Justin Pierce
Modified: 2018-07-30 20:48 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2018-07-30 20:48:15 UTC
Target Upstream Version:

Attachments (Terms of Use)

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):

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

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

$ git tag --contains 0f1103b222705421380805acae4c56bb462e9b3f

Duping to 3.10 bz 1603611 for above mentioned issue.

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

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