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

Bug 1970410

Summary: CNF test container: [SNO] [dpdk] All dpdk tests failed : Couldn`t create NetworkAttachmentDefinition CR
Product: OpenShift Container Platform Reporter: elevin
Component: CNF Platform ValidationAssignee: Sebastian Scheinkman <sscheink>
Status: CLOSED DUPLICATE QA Contact: Nikita <nkononov>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.8CC: aos-bugs, sscheink
Target Milestone: ---   
Target Release: ---   
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: 2021-06-14 15:36:56 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 2021-06-10 12:41:02 UTC
Description of problem:
All DPDK tests failed in regular mode on SNO cluster.

2021-06-10T12:25:17.724Z	ERROR	controllers.SriovNetwork	Couldn't create NetworkAttachmentDefinition CR	{"sriovnetwork": "openshift-sriov-network-operator/test-dpdk-network", "Namespace": "dpdk-testing", "Name": "test-dpdk-network", "error": "Internal error occurred: failed calling webhook \"multus-validating-config.k8s.io\": Post \"https://multus-admission-controller.openshift-multus.svc:443/validate?timeout=30s\": x509: certificate signed by unknown authority"}


Version-Release number of selected component (if applicable):
Client Version: 4.8.0-0.nightly-2021-06-08-034312
Server Version: 4.8.0-0.nightly-2021-06-08-034312
Kubernetes Version: v1.21.0-rc.0+fec6fbc
DPDK_TESTS_IMAGE=dpdk-base:v4.8.0-8
CNF_TESTS_IMAGE=openshift4-cnf-tests:v4.8.0-48


How reproducible:


Steps to Reproduce:
1.SNO cluster
2.podman run  --net=host -v /root/ocp/auth:/kubeconfig:Z  -e KUBECONFIG=/kubeconfig/kubeconfig -e IMAGE_REGISTRY=cnfdc8-installer:5000/rh-osbs/ -e CNF_TESTS_IMAGE=openshift4-cnf-tests:v4.8.0-48 -e DPDK_TESTS_IMAGE=dpdk-base:v4.8.0-8 -e ROLE_WORKER_CNF=master -e SCTPTEST_HAS_NON_CNF_WORKERS=false registry-proxy.engineering.redhat.com/rh-osbs/openshift4-cnf-tests:v4.8.0-48 /usr/bin/test-run.sh -ginkgo.focus="dpdk"


Actual results:

• Failure in Spec Setup (BeforeEach) [1988.664 seconds]
dpdk
/remote-source/app/cnf-tests/testsuites/e2esuite/dpdk/dpdk.go:92
  VFS allocated for dpdk
  /remote-source/app/cnf-tests/testsuites/e2esuite/dpdk/dpdk.go:151
    Validate the build [BeforeEach]
    /remote-source/app/cnf-tests/testsuites/e2esuite/dpdk/dpdk.go:173
      Should forward and receive packets from a pod running dpdk base on a image created by building config
      /remote-source/app/cnf-tests/testsuites/e2esuite/dpdk/dpdk.go:174
      Timed out after 10.001s.
      Unexpected error:
          <*errors.StatusError | 0xc0004d8960>: {
              ErrStatus: {
                  TypeMeta: {Kind: "", APIVersion: ""},
                  ListMeta: {
                      SelfLink: "",
                      ResourceVersion: "",
                      Continue: "",
                      RemainingItemCount: nil,
                  },
                  Status: "Failure",
                  Message: "network-attachment-definitions.k8s.cni.cncf.io \"test-dpdk-network\" not found",
                  Reason: "NotFound",
                  Details: {
                      Name: "test-dpdk-network",
                      Group: "k8s.cni.cncf.io",
                      Kind: "network-attachment-definitions",
                      UID: "",
                      Causes: nil,
                      RetryAfterSeconds: 0,
                  },
                  Code: 404,
              },
          }
          network-attachment-definitions.k8s.cni.cncf.io "test-dpdk-network" not found
      occurred
      /remote-source/app/cnf-tests/testsuites/e2esuite/dpdk/dpdk.go:892
Expected results:


Additional info:

Comment 1 Sebastian Scheinkman 2021-06-14 15:36:56 UTC

*** This bug has been marked as a duplicate of bug 1970409 ***