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

Metallb FRR-K8s: frr-k8s daemonset using quay.io/metallb/frr-k8s image

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • 4.16.0
    • Networking / Metal LB
    • None
    • +
    • Important
    • CNF Network Sprint 255
    • 1
    • False
    • Hide

      None

      Show
      None
    • When deploying with FRR-K8s as the BGP backend for metallb, the metallb operator deploys the upstream image instead of the dowstream one.
    • In Progress

      Description of problem:

      $ oc get pods -n metallb-system 
      NAME                                                   READY   STATUS                  RESTARTS   AGE
      controller-5b95759866-xlqmw                            2/2     Running                 0          89s
      frr-k8s-6xnz4                                          0/6     Init:ImagePullBackOff   0          90s
      frr-k8s-8vqxl                                          0/6     Init:ImagePullBackOff   0          90s
      frr-k8s-cmjd4                                          0/6     Init:ImagePullBackOff   0          90s
      frr-k8s-f4t5t                                          0/6     Init:ImagePullBackOff   0          90s
      frr-k8s-szvxp                                          0/6     Init:ImagePullBackOff   0          90s
      frr-k8s-webhook-server-7456d497f9-t7nkw                0/1     ImagePullBackOff        0          90s
      

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

      4.16.0-rc.5
      metallb-operator.v4.16.0-202406131906

       

      How reproducible:

      100%

      Steps to Reproduce:

      1.enabled FRR-K8s mode
       2.
      3.
      

      Actual results:

      Events:
        Type     Reason     Age                 From               Message
        ----     ------     ----                ----               -------
        Normal   Scheduled  112s                default-scheduler  Successfully assigned metallb-system/frr-k8s-6xnz4 to worker-1
        Normal   Pulled     112s                kubelet            Container image "registry.redhat.io/openshift4/frr-rhel9@sha256:31484cbf9f70936a81685f64f51bc1d78897b3cbd0b5e4ab54710dc765d62837" already present on machine
        Normal   Created    112s                kubelet            Created container cp-frr-files
        Normal   Started    112s                kubelet            Started container cp-frr-files
        Warning  Failed     99s (x2 over 111s)  kubelet            Failed to pull image "quay.io/metallb/frr-k8s:v0.0.11": RegistryUnavailable: pinging container registry quay.io: Get "https://quay.io/v2/": dial tcp 54.92.180.23:443: connect: connection refused
        Warning  Failed     70s                 kubelet            Failed to pull image "quay.io/metallb/frr-k8s:v0.0.11": RegistryUnavailable: pinging container registry quay.io: Get "https://quay.io/v2/": dial tcp 54.221.103.142:443: connect: connection refused
        Normal   Pulling    16s (x4 over 111s)  kubelet            Pulling image "quay.io/metallb/frr-k8s:v0.0.11"
        Warning  Failed     16s (x4 over 111s)  kubelet            Error: RegistryUnavailable
        Warning  Failed     16s                 kubelet            Failed to pull image "quay.io/metallb/frr-k8s:v0.0.11": RegistryUnavailable: pinging container registry quay.io: Get "https://quay.io/v2/": dial tcp 34.226.34.72:443: connect: connection refused
        Normal   BackOff    2s (x5 over 85s)    kubelet            Back-off pulling image "quay.io/metallb/frr-k8s:v0.0.11"
        Warning  Failed     2s (x5 over 85s)    kubelet            Error: ImagePullBackOff
      

      Expected results:

       

      Additional info:

      metallb MetalLB deploy should work when deployed with BGP type FRR-K8s Mode
      /home/kni/cnf_tests_dir/cnf-tests/cnf-tests/submodules/metallb-operator/test/e2e/functional/tests/e2e.go:312
        STEP: setting the bgpType @ 06/18/24 11:39:51.565
        STEP: checking the controller is running in the right bgp mode @ 06/18/24 11:39:51.576
        STEP: checking MetalLB controller deployment is in running state @ 06/18/24 11:39:52.213
        STEP: checking the speaker is running in the right bgp mode @ 06/18/24 11:39:56.253
        STEP: checking MetalLB daemonset is in running state @ 06/18/24 11:39:56.256
        STEP: checking MetalLB CR status is set @ 06/18/24 11:39:56.269
        STEP: checking frr-k8s daemonset is in running state @ 06/18/24 11:40:21.31
        [FAILED] in [It] - /home/kni/cnf_tests_dir/cnf-tests/cnf-tests/submodules/metallb-operator/test/e2e/functional/tests/e2e.go:281 @ 06/18/24 11:43:44.551
      • [FAILED] [235.366 seconds]
      metallb MetalLB deploy should work when deployed with BGP type [It] FRR-K8s Mode
      /home/kni/cnf_tests_dir/cnf-tests/cnf-tests/submodules/metallb-operator/test/e2e/functional/tests/e2e.go:312  [FAILED] Timed out after 180.001s.
        Unexpected error:
            <*errors.errorString | 0xc00023ade0>: 
            daemonset speaker pod frr-k8s-6xnz4 is not running, expected status Running got Pending
            {
                s: "daemonset speaker pod frr-k8s-6xnz4 is not running, expected status Running got Pending",
            }
        occurred
        In [It] at: /home/kni/cnf_tests_dir/cnf-tests/cnf-tests/submodules/metallb-operator/test/e2e/functional/tests/e2e.go:281 @

            fpaoline@redhat.com Federico Paolinelli
            rhn-cnf-elevin Evgeny Levin
            Arti Sood Arti Sood
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: