Bug 2104669 - cnf-tests: MetalLB: MetalLB deploy should have MetalLB pods in running state. Test is in failed state constantly
Summary: cnf-tests: MetalLB: MetalLB deploy should have MetalLB pods in running state....
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.9
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.9.z
Assignee: Carlos Goncalves
QA Contact: Nikita
URL:
Whiteboard:
Depends On: 2094679
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-07-06 20:07 UTC by Nikita
Modified: 2022-09-12 13:37 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-09-12 13:36:57 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift-kni cnf-features-deploy pull 1210 0 None open Bug 2104669: pin metallb-operator to openshift/metallb-operator@release-4.9 2022-08-15 09:43:54 UTC
Github openshift metallb-operator pull 110 0 None open Bug 2104669: Move tests and suites to different packages 2022-08-05 11:10:24 UTC
Github openshift metallb-operator pull 89 0 None open Bug 2104669: Check that deployment ready replicas greater than zero 2022-07-07 10:15:03 UTC
Red Hat Bugzilla 2068600 0 medium CLOSED cnf-tests: MetalLB: MetalLB deploy should have MetalLB pods in running state. Test is in failed state constantly 2022-07-27 02:25:17 UTC
Red Hat Product Errata RHBA-2022:6408 0 None None None 2022-09-12 13:37:10 UTC

Description Nikita 2022-07-06 20:07:00 UTC 
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
Comment 7 Greg Kopels 2022-08-25 12:48:47 UTC 
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  ------------------------------
Comment 9 errata-xmlrpc 2022-09-12 13:36:57 UTC 
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
Note You need to log in before you can comment on or make changes to this bug.