Bug 1994060
| Summary: | API response for host routes includes misleading family number when IPv6 is enabled | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Constantin Vultur <cvultur> |
| Component: | assisted-installer | Assignee: | Ori Amizur <oamizur> |
| assisted-installer sub component: | assisted-service | QA Contact: | Yuri Obshansky <yobshans> |
| Status: | CLOSED ERRATA | Docs Contact: | |
| Severity: | medium | ||
| Priority: | unspecified | CC: | aos-bugs, jgil, lgamliel |
| Version: | 4.9 | ||
| Target Milestone: | --- | ||
| Target Release: | 4.9.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | OCP-Metal-V1.0.25.2 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-10-18 17:46:44 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: | |||
Verified with OCP-Metal-V1.0.25.2 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 (Moderate: OpenShift Container Platform 4.9.0 bug fix and security update), 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-2021:3759 |
Description of problem: API response for host routes shows family 4/6 with combined IPv4/IPv6 addresses Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Create cluster and download iso 2. On one VM add 2 nics, one with IPv4 , one with IPv6 3. Boot ISO and register with service 4. Check the API response for cluster and pipe it with: | jq -r .hosts[].inventory | jq .routes Actual results: Reported routes include combination of family: 6 with IPv4 addresses like: { "destination": "52.44.175.248", "family": 6, "gateway": "192.168.123.1", "interface": "enp0s3" }, { "destination": "192.168.123.0", "family": 6, "interface": "enp0s3" }, Or "family": 4 with IPv6 addresses: { "destination": "fe80::", "family": 4, "interface": "cni-podman0" }, { "destination": "0.0.0.0", "family": 4, "gateway": "fe80::5054:ff:febf:4214", "interface": "enp0s4" }, Expected results: The ipv4/ipv6 routes should not be with mixed information. Additional info: