-
Bug
-
Resolution: Done
-
Undefined
-
None
-
4.11
-
No
-
CNF Network Sprint 237
-
1
-
False
-
Description of problem:
Failed test: metallb MetalLB deploy should have MetalLB pods in running state failed
Version-Release number of selected component (if applicable):
4.11
How reproducible:
CI job
Steps to Reproduce:
1. Run periodic-ci-openshift-release-master-nightly-4.11-e2e-telco5g-cnftests 2. Look at test results
Actual results:
Failures:
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/1666211278558859264/artifacts/e2e-telco5g-cnftests/telco5g-cnf-tests/artifacts/test_results.html
with the following error:
ft3.1: [BeforeEach] MetalLB deploy
/tmp/cnf-P3oMg/cnf-features-deploy/vendor/github.com/metallb/metallb-operator/test/e2e/functional/tests/e2e.go:41
[It] should have MetalLB pods in running state
/tmp/cnf-P3oMg/cnf-features-deploy/vendor/github.com/metallb/metallb-operator/test/e2e/functional/tests/e2e.go:71
�[1mSTEP�[0m: checking MetalLB controller deployment is in running state
�[1mSTEP�[0m: checking MetalLB daemonset is in running state
[AfterEach] MetalLB deploy
/tmp/cnf-P3oMg/cnf-features-deploy/vendor/github.com/metallb/metallb-operator/test/e2e/functional/tests/e2e.go:55
/tmp/cnf-P3oMg/cnf-features-deploy/vendor/github.com/metallb/metallb-operator/test/e2e/functional/tests/e2e.go:71
Timed out after 180.001s.
Expected
<bool>: false
to be true
/tmp/cnf-P3oMg/cnf-features-deploy/vendor/github.com/metallb/metallb-operator/test/e2e/functional/tests/e2e.go:101
Expected results:
Pass
Additional info:
See grafana results in the following link: https://snapshots.raintank.io/dashboard/snapshot/5ReWotsSWZNtFKwE3mYuEeuVOD00vIUS