Bug 2100035
| Summary: | Advertising ipv4 via ipv6 and viceversa is broken in 4.11 | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Federico Paolinelli <fpaoline> |
| Component: | Networking | Assignee: | Federico Paolinelli <fpaoline> |
| Networking sub component: | Metal LB | QA Contact: | Greg Kopels <gkopels> |
| Status: | CLOSED ERRATA | Docs Contact: | |
| Severity: | medium | ||
| Priority: | medium | CC: | asood, elevin, gkopels, kuiwang, mifiedle |
| Version: | 4.11 | ||
| Target Milestone: | --- | ||
| Target Release: | 4.12.0 | ||
| 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: | 2023-01-18 11:51:58 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: | 2102158 | ||
| Bug Blocks: | |||
|
Description
Federico Paolinelli
2022-06-22 08:48:32 UTC
Hi, Is it possible to see the working Speaker FRR configuration used in 4.10? Thanks Greg I am also available on Slack Tried deploying http://registry.ci.openshift.org/ocp/release:4.11.0-0.nightly-2022-07-19-104004 but having the same issue [gkopels@ ~]$ oc get nodes NAME STATUS ROLES AGE VERSION hlxcl7-master-0.hlxcl7.lab.eng.tlv2.redhat.com NotReady master 42m v1.24.0+9546431 hlxcl7-master-1.hlxcl7.lab.eng.tlv2.redhat.com NotReady master 42m v1.24.0+9546431 hlxcl7-master-2.hlxcl7.lab.eng.tlv2.redhat.com NotReady master 42m v1.24.0+9546431 https://auto-jenkins-csb-kniqe.apps.ocp-c1.prod.psi.redhat.com/job/CNF/job/ocp-deploy-BM/704/console If required I can provide access to the cluster. If required I can provide access to the cluster. If required I can provide access to the cluster. Again I have aplogize I have mixed up the two different bugs. I am unable to validate this bug because of follwoing bz in which 4.11 dual stack deployment fails https://bugzilla.redhat.com/show_bug.cgi?id=2102158 Hi gkopels,
The following bugs have been added to advisory, please help to verify them ASAP. If you have any concerns or any bugs cannot be verified, please contact with errata owner yinzhou. Thank you!
Candidate Build: quay.io/openshift-release-dev/ocp-release:4.11.0-rc.5-x86_64
Advisory: https://errata.devel.redhat.com/advisory/97036
ASSIGNED N https://bugzilla.redhat.com/show_bug.cgi?id=2100035
* I am currently unable to test this candidate build because of the following bz which is blocking dualstack deployment.
https://bugzilla.redhat.com/show_bug.cgi?id=2110029
Verification blocked on 4.11.0 - move to 4.11.z Verification of this bug is currently blocked by bz https://bugzilla.redhat.com/show_bug.cgi?id=2102158 This bz is still blocked by the following bug https://bugzilla.redhat.com/show_bug.cgi?id=2102158 bug https://bugzilla.redhat.com/show_bug.cgi?id=2102158 has been validated now it is possible to validate this bug Hi I have configured a dual stack. I am able to advertise ipv6 and ipv4 routes with two neighbors configured one as ipv4 and the other ipv6. I attempted to configure the speaker with the configuration that Arti supplied with only an ipv4 peer and only the ipv4 route was advertised. Do we know how the customer configured BGP? I also attempted advertising a ipv4 route over a ipv6 peer. The ipv4 route was not advertised. router bgp 64500 no bgp ebgp-requires-policy no bgp default ipv4-unicast no bgp network import-check neighbor 2620:52:0:2e38::131 remote-as 64500 neighbor 2620:52:0:2e38::131 password bgp-test neighbor 2620:52:0:2e38::131 timers 30 90 ! address-family ipv4 unicast network 4.4.4.100/32 redistribute connected neighbor 2620:52:0:2e38::131 activate exit-address-family ! address-family ipv6 unicast network 2001:192:4::/124 network 2001:192:4::2000/124 network fd01:0:0:5::/64 redistribute connected neighbor 2620:52:0:2e38::131 activate exit-address-family OCP version 4.10.45 When configured dualstack bgp peers I am able to advertise both ipv4 and ipv6 routes. However similar to the above OCP version 4.11.20 I am unable to propagate ipv6 routes over a ipv4 bgp peer. The same is true when attempting to advertise ipv4 routes over a ipv6 bgp peer. router bgp 64500 no bgp ebgp-requires-policy no bgp default ipv4-unicast no bgp network import-check neighbor 10.46.56.131 remote-as 64500 neighbor 10.46.56.131 password bgp-test neighbor 10.46.56.131 timers 30 90 ! address-family ipv4 unicast network 4.4.4.0/24 neighbor 10.46.56.131 activate neighbor 10.46.56.131 route-map 10.46.56.131-in in exit-address-family ! address-family ipv6 unicast network 2001:192:4::/124 neighbor 10.46.56.131 activate neighbor 10.46.56.131 route-map 10.46.56.131-in in exit-address-family The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days |