Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2072709

Summary: DPDK: pod mac duplcation in context "VFS allocated for dpdk"
Product: OpenShift Container Platform Reporter: elevin
Component: CNF Platform ValidationAssignee: Sebastian Scheinkman <sscheink>
Status: CLOSED ERRATA QA Contact: Nikita <nkononov>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.9CC: aos-bugs, eglottma, grajaiya, mcornea, sscheink
Target Milestone: ---   
Target Release: 4.11.0   
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-08-10 12:16:31 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:

Description elevin 2022-04-06 19:55:43 UTC
Description of problem:
CNF Features e2e integration tests.dpdk VFS allocated for dpdk Validate the build Should forward and receive packets from a pod running dpdk base on a image created by building config


Stacktrace
/remote-source/app/cnf-tests/testsuites/pkg/execute/ginkgo.go:9
Unexpected error:
    <*errors.errorString | 0xc000438f20>: {
        s: "timed out waiting for the condition",
    }
    timed out waiting for the condition
occurred
/remote-source/app/cnf-tests/testsuites/e2esuite/dpdk/dpdk.go:306



Second pod can not be created due to mac duplication

[4:05 PM]   Warning  FailedCreatePodSandBox  52s   kubelet            Failed to create pod sandbox: rpc error: code = Unknown desc = failed to create pod network sandbox k8s_dpdk-cc7dj_dpdk-testing_f6cc827e-3728-45d2-a558-78aa598c1685_0(2d2d66facb9e60edac39e322cd4d2e6c91f2855a237e76dbf53b1d7937a75075): error adding pod dpdk-testing_dpdk-cc7dj to CNI network "multus-cni-network": [dpdk-testing/dpdk-cc7dj/f6cc827e-3728-45d2-a558-78aa598c1685:test-dpdk-network]: error adding container to network "test-dpdk-network": SRIOV-CNI failed to configure VF "failed to set MAC address to 60:00:00:00:00:01: invalid argument"

https://github.com/openshift-kni/cnf-features-deploy/blob/release-4.9/cnf-tests/testsuites/e2esuite/dpdk/dpdk.go#L292-L306

Version-Release number of selected component (if applicable):
4.9
E810 NIC
How reproducible:
100%

Steps to Reproduce:
1.  podman run --name cnf-container-tests  --net=host -v /home/kni/du_credentials/kni-qe-1/auth:/kubeconfig:Z -e KUBECONFIG=/kubeconfig/kubeconfig -e IMAGE_REGISTRY=registry.kni-qe-0.lab.eng.rdu2.redhat.com:5000/ -e CNF_TESTS_IMAGE=cnf-tests-rhel8:v4.9 -e DPDK_TESTS_IMAGE=dpdk-base-rhel8:latest -e NODES_SELECTOR=node-role.kubernetes.io/master= -e ROLE_WORKER_CNF=master -e DISCOVERY_MODE=true -e PERF_TEST_PROFILE=openshift-node-performance-profile -e SCTPTEST_HAS_NON_CNF_WORKERS=false registry.redhat.io/openshift4/cnf-tests-rhel8:v4.9 /usr/bin/test-run.sh  -ginkgo.focus="dpdk"

2.
3.

Actual results:


Expected results:


Additional info:

Comment 3 elevin 2022-08-01 09:17:04 UTC
OCP 4.9.43
registry-proxy.engineering.redhat.com/rh-osbs/openshift4-cnf-tests:v4.9.11-2

==================================================================
• [SLOW TEST:59.454 seconds]
dpdk
/remote-source/app/cnf-tests/testsuites/e2esuite/dpdk/dpdk.go:117
  VFS allocated for dpdk
  /remote-source/app/cnf-tests/testsuites/e2esuite/dpdk/dpdk.go:294
    Validate a DPDK workload running inside a pod
    /remote-source/app/cnf-tests/testsuites/e2esuite/dpdk/dpdk.go:339
      Should forward and receive packets
      /remote-source/app/cnf-tests/testsuites/e2esuite/dpdk/dpdk.go:340

Comment 4 elevin 2022-08-03 10:19:47 UTC
Verified on openshift4-cnf-tests:v4.11.0-51

Comment 7 errata-xmlrpc 2022-08-10 12:16:31 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.11 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:5869