Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-54894

[BGP LGW] RA failed to advertise pod network routes to external frr

    • None
    • None
    • Rejected
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Description of problem:

      Using image which built via 2239 in 8th Apri, on some of our clusters, after creating ra, it may take 2~3 minutes to update the status, and without frrconfiguration applied, it still moved to "accepted" status. After all configuration done (cudn, ns, pods, ra, frr, external frr, etc), pod network route is not advertised to external frr. 
      
      Checked on ovnkube-control-plane pods and found error below:
      ...
      network: default
      I0411 07:39:45.504904       1 controller.go:262] Finished syncing routeadvertisements "default", took 56.493µs
      I0411 07:39:45.504938       1 controller.go:257] Controller clustermanager routeadvertisements controller: error found while processing default: failed to reconcile RouteAdvertisements "default": BGP is currenty not supported for Layer2 networks in local gateway mode, network: default

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

      4.19

      How reproducible:

      always on some clusters

      Steps to Reproduce:

      1. convert cluster to LGW

      2. enable FRR and RA

      3. configure RA first and then FRR as below

      # cat ra.yaml 
      apiVersion: k8s.ovn.org/v1
      kind: RouteAdvertisements
      metadata:
        name: default
      spec:
        networkSelector:
          matchLabels:
            k8s.ovn.org/default-network: ""
        advertisements:
        - "PodNetwork"
        - "EgressIP"
      
      # cat frr.yaml 
      apiVersion: frrk8s.metallb.io/v1beta1
      kind: FRRConfiguration
      metadata:
        name: receive-all
        namespace: openshift-frr-k8s
      spec:
        bgp:
          routers:
          - asn: 64512
            neighbors:
            - address: 192.168.111.1
              disableMP: true
              asn: 64512
              toReceive:
                allowed:
                  mode: all 

      4. delete frrconfigration first and then delete ra, and recreate ra. RA may take 2-3 minutes to udpate status and moved to 'accepted' without frrconfiguration applied. 

      5. configure frrconfiguration and start exteral frr. 

      6. check routes on external frr and found that no bgp routes advertised.

      Actual results:

      RA is "accepted" without FRRConfiguration applied, and it doesn't advertise podnetwork routes to external frr.

      Expected results:

      • RA should report 'no FRRConfigurations selected' when no frrconfiguration applied
      • RA should advertise podnetwork routes to external frr.

              pdiak@redhat.com Patryk Diak
              rhn-support-yingwang Ying Wang
              Ying Wang Ying Wang
              None
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: