Bug 1489023
| Summary: | [3.4 Backport] Can not start atomic-openshift-node if the system does not have a default route | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Eric Rich <erich> |
| Component: | Networking | Assignee: | Jacob Tanenbaum <jtanenba> |
| Status: | CLOSED ERRATA | QA Contact: | Meng Bo <bmeng> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 3.5.1 | CC: | aos-bugs, asolanas, bbennett, bmeng, dcbw, decarr, eparis, erich, hongli, jokerman, mmccomas, pcameron, smunilla, xtian |
| Target Milestone: | --- | ||
| Target Release: | 3.4.z | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Cause: the OpenShift node proxy previously did not support using a specified IP address.
Consequence: this bug could prevent correct operation on hosts with multiple network interface cards.
Fix: the OpenShift node process already accepts a "--bind-address=<ip address>:<port>" command-line flag and "bindAddress:" config file option for the multiple network interface card case. The proxy functionality has been fixed to respect these options.
Result: when --bind-address or bindAddress are used, the OpenShift node proxy should work correctly when the OpenShift node host has multiple network interface cards
|
Story Points: | --- |
| Clone Of: | 1462428 | Environment: | |
| Last Closed: | 2017-12-07 07:11:23 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: | |||
| Bug Depends On: | 1462428 | ||
| Bug Blocks: | |||
|
Comment 1
Ben Bennett
2017-09-13 20:09:35 UTC
verified in atomic-openshift-3.4.1.44.33-1.git.0.d72524e and issue has been fixed. 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:3389 |