Bug 2100035 - Advertising ipv4 via ipv6 and viceversa is broken in 4.11
Summary: Advertising ipv4 via ipv6 and viceversa is broken in 4.11
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.11
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.12.0
Assignee: Federico Paolinelli
QA Contact: Greg Kopels
URL:
Whiteboard:
Depends On: 2102158
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-06-22 08:48 UTC by Federico Paolinelli
Modified: 2023-09-18 04:39 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-01-18 11:51:58 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift metallb pull 67 0 None open Bug 2100035: Fix MP BGP 2022-06-22 08:49:10 UTC

Description Federico Paolinelli 2022-06-22 08:48:32 UTC
Description of problem:

Found by an upstream user. 
Advertising an ipv4 address to a router connected via an ipv6 session and viceversa was working in 4.10 but was broken in 4.11


Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 3 Greg Kopels 2022-06-27 14:29:44 UTC
Hi,
Is it possible to see the working Speaker FRR configuration used in 4.10?
Thanks Greg
I am also available on Slack

Comment 7 Greg Kopels 2022-07-22 02:28:33 UTC
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

Comment 8 Greg Kopels 2022-07-22 03:36:11 UTC
If required I can provide access to the cluster.

Comment 9 Greg Kopels 2022-07-22 03:36:20 UTC
If required I can provide access to the cluster.

Comment 10 Greg Kopels 2022-07-22 03:36:37 UTC
If required I can provide access to the cluster.

Comment 11 Greg Kopels 2022-07-22 03:42:46 UTC
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

Comment 12 Greg Kopels 2022-07-26 17:44:40 UTC
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

Comment 13 Mike Fiedler 2022-08-03 12:32:10 UTC
Verification blocked on 4.11.0 - move to 4.11.z

Comment 16 Greg Kopels 2022-08-18 08:56:50 UTC
Verification of this bug is currently blocked by bz https://bugzilla.redhat.com/show_bug.cgi?id=2102158

Comment 19 Greg Kopels 2022-08-24 12:23:41 UTC
This bz is still blocked by the following bug https://bugzilla.redhat.com/show_bug.cgi?id=2102158

Comment 27 Greg Kopels 2022-11-13 11:34:45 UTC
bug https://bugzilla.redhat.com/show_bug.cgi?id=2102158 has been validated now it is possible to validate this bug

Comment 28 Greg Kopels 2023-01-15 12:30:09 UTC
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?

Comment 29 Greg Kopels 2023-01-15 16:25:10 UTC
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

Comment 31 Greg Kopels 2023-01-16 10:00:31 UTC
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

Comment 33 Red Hat Bugzilla 2023-09-18 04:39:52 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days


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