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

[4.12] MetalLB contains incorrect data Correct and incorrect MetalLB resources coexist should have correct statuses

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • 4.12, 4.11
    • Networking / Metal LB
    • No
    • CNF Network Sprint 238
    • 1
    • False
    • Hide

      None

      Show
      None

      This is a clone of issue OCPBUGS-8433. The following is the description of the original issue:
      —
      Description of problem:

      metallb MetalLB contains incorrect data Correct and incorrect MetalLB resources coexist should have correct statuses

ft11.3: [BeforeEach] Correct and incorrect MetalLB resources coexist
  /tmp/cnf-90qND/cnf-features-deploy/vendor/github.com/metallb/metallb-operator/test/e2e/functional/tests/e2e.go:184
[It] should have correct statuses
  /tmp/cnf-90qND/cnf-features-deploy/vendor/github.com/metallb/metallb-operator/test/e2e/functional/tests/e2e.go:200
�[1mSTEP�[0m: checking MetalLB resource status
[AfterEach] Correct and incorrect MetalLB resources coexist
  /tmp/cnf-90qND/cnf-features-deploy/vendor/github.com/metallb/metallb-operator/test/e2e/functional/tests/e2e.go:196
/tmp/cnf-90qND/cnf-features-deploy/vendor/github.com/metallb/metallb-operator/test/e2e/functional/tests/e2e.go:200
Timed out after 30.001s.
Expected
    <bool>: false
to be true
/tmp/cnf-90qND/cnf-features-deploy/vendor/github.com/metallb/metallb-operator/test/e2e/functional/tests/e2e.go:214

Examples:
https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/origin-ci-test/logs/periodic-ci-openshift-release-master-nightly-4.12-e2e-telco5g-cnftests/1630448411150913536/artifacts/e2e-telco5g-cnftests/telco5g-cnf-tests/artifacts/test_results.html

https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/origin-ci-test/logs/periodic-ci-openshift-release-master-nightly-4.12-e2e-telco5g-cnftests/1631535422083436544/artifacts/e2e-telco5g-cnftests/telco5g-cnf-tests/artifacts/test_results.html

https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/origin-ci-test/logs/periodic-ci-openshift-release-master-nightly-4.11-e2e-telco5g-cnftests/1630697303427780608/artifacts/e2e-telco5g-cnftests/telco5g-cnf-tests/artifacts/test_results.html

https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/origin-ci-test/logs/periodic-ci-openshift-release-master-nightly-4.11-e2e-telco5g-cnftests/1631060453771710464/artifacts/e2e-telco5g-cnftests/telco5g-cnf-tests/artifacts/test_results.html

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

      4.11 upstream ci jobs
4.12 upstream ci jobs

      How reproducible:

      Consistently reproducible in the latest 4.11/4.12 telco5g-cnftests ci jobs.

      Steps to Reproduce:

      1. Run 4.11-e2e-telco5g-cnftests /  4.12-e2e-telco5g-cnftests prow job 
2.
3.

      Actual results:

      Test fail

      Expected results:

      Test pass

      Additional info:

              lnoy@redhat.com Lior Noy (Inactive)
              openshift-crt-jira-prow OpenShift Prow Bot
              Arti Sood Arti Sood
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: