Bug 2104669
| Summary: | cnf-tests: MetalLB: MetalLB deploy should have MetalLB pods in running state. Test is in failed state constantly | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Nikita <nkononov> |
| Component: | Networking | Assignee: | Carlos Goncalves <cgoncalves> |
| Networking sub component: | Metal LB | QA Contact: | Nikita <nkononov> |
| Status: | CLOSED ERRATA | Docs Contact: | |
| Severity: | medium | ||
| Priority: | medium | CC: | cgoncalves, gkopels |
| Version: | 4.9 | ||
| Target Milestone: | --- | ||
| Target Release: | 4.9.z | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-09-12 13:36:57 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 2094679 | ||
| Bug Blocks: | |||
Fix validated with cnf-tests-container-v4.9.11-5 15:44:32 • [SLOW TEST:5.879 seconds] 15:44:32 metallb 15:44:32 /remote-source/app/vendor/github.com/metallb/metallb-operator/test/e2e/functional/tests/e2e.go:41 15:44:32 Testing create/delete Multiple AddressPools 15:44:32 /remote-source/app/vendor/github.com/metallb/metallb-operator/test/e2e/functional/tests/e2e.go:323 15:44:32 should have created, merged and deleted resources correctly 15:44:32 /remote-source/app/vendor/github.com/metallb/metallb-operator/test/e2e/functional/tests/e2e.go:324 15:44:32 ------------------------------ Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (OpenShift Container Platform 4.9.48 low-latency extras update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2022:6408 |
Description of problem: cnf-tests: MetalLB: MetalLB deploy should have MetalLB pods in running state is failing over last 5 z-stream releases. • Failure [4.391 seconds] metallb /remote-source/app/vendor/github.com/metallb/metallb-operator/test/e2e/functional/tests/e2e.go:41 MetalLB deploy /remote-source/app/vendor/github.com/metallb/metallb-operator/test/e2e/functional/tests/e2e.go:42 should have MetalLB pods in running state [It] /remote-source/app/vendor/github.com/metallb/metallb-operator/test/e2e/functional/tests/e2e.go:76 Expected <v1.PodPhase>: Pending to equal <v1.PodPhase>: Running /remote-source/app/vendor/github.com/metallb/metallb-operator/test/e2e/functional/tests/e2e.go:95 ------------------------------ Version-Release number of selected component (if applicable): OCP version: Same issue occur on: 4.9.19-4.9.25 cnf-test version: openshift4-cnf-tests:v4.9.7-11 How reproducible: Run metal-lb test suite on freshly installed OCP 4.9 using openshift4-cnf-openshift4-cnf-tests:v4.9.10-8 container image