Bug 1757777
Summary: | hostIP and podIP differs with hostNetwork: true | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Radim Vansa <rvansa> |
Component: | Networking | Assignee: | Dan Winship <danw> |
Networking sub component: | openshift-sdn | QA Contact: | zhaozhanqi <zzhao> |
Status: | CLOSED ERRATA | Docs Contact: | |
Severity: | medium | ||
Priority: | unspecified | CC: | bbennett, pehunt |
Version: | 4.1.z | ||
Target Milestone: | --- | ||
Target Release: | 4.3.0 | ||
Hardware: | x86_64 | ||
OS: | All | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2020-05-13 21:26:26 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
Radim Vansa
2019-10-02 12:29:48 UTC
This is not a regression in 4.2.0 (and I suspect it's behaved like this forever). Pushing to 4.3.0 to consider the solution, and then we can decide if it merits a backport. Dan, I think you fixed this with the latest CRIO changes for ipv6, right? Yes, this has been fixed with the changes that recently got merged into 1.16 Verified this bug on 4.3.0-0.nightly-2019-11-13-233341 <none> openshift-monitoring node-exporter-6k6dh 2/2 Running 0 161m 192.168.0.18 <none> <none> openshift-monitoring node-exporter-9kmdk 2/2 Running 0 74m 192.168.0.29 <none> <none> openshift-monitoring node-exporter-dgjxm 2/2 Running 0 161m 192.168.0.16 <none> <none> openshift-monitoring node-exporter-h9nr4 2/2 Running 0 161m 192.168.0.13 <none> <none> openshift-monitoring node-exporter-hnwtt 2/2 Running 0 161m 192.168.0.22 <none> <none> openshift-monitoring node-exporter-kxc8c 2/2 Running 0 161m 192.168.0.20 <none> <none> openshift-monitoring node-exporter-x6mvr 2/2 Running 0 161m 192.168.0.14 <none> <none> 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-2020:0062 |