Bug 1879926

Summary: [Serial][sig-node][Feature:TopologyManager] Configured cluster with gu workload attached to SRIOV networks should let resource-aligned PODs have working SRIOV network interface
Product: OpenShift Container Platform Reporter: Devan Goodwin <dgoodwin>
Component: NodeAssignee: Ryan Phillips <rphillips>
Status: CLOSED DUPLICATE QA Contact: Sunil Choudhary <schoudha>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.6CC: aos-bugs, jokerman
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:
[Serial][sig-node][Feature:TopologyManager] Configured cluster with gu workload attached to SRIOV networks should let resource-aligned PODs have working SRIOV network interface [Serial][sig-node][Feature:TopologyManager] Configured cluster with gu workload saturating NUMA nodes should allow a pod requesting as many cores as a full NUMA node have [Serial][sig-node][Feature:TopologyManager] Configured cluster with gu workload saturating NUMA nodes should guarantee correct allocation with concurrent creation [Serial][sig-node][Feature:TopologyManager] Configured cluster with gu workload saturating NUMA nodes should reject pod requesting more cores than a single NUMA node have [Serial][sig-node][Feature:TopologyManager] Configured cluster with gu workload should guarantee NUMA-aligned cpu cores in gu pods with multiple pods, each with a single container requesting 1 core, 1 device Serial][sig-node][Feature:TopologyManager] Configured cluster with gu workload should guarantee NUMA-aligned cpu cores in gu pods with multiple pods, each with a single container requesting 2 core, 1 device [Serial][sig-node][Feature:TopologyManager] Configured cluster with gu workload should guarantee NUMA-aligned cpu cores in gu pods with multiple pods, each with multiple containers requesting 1 core, 1 device [Serial][sig-node][Feature:TopologyManager] Configured cluster with gu workload should guarantee NUMA-aligned cpu cores in gu pods with multiple pods, each with multiple containers requesting 1 core, only one requesting 1 device [Serial][sig-node][Feature:TopologyManager] Configured cluster with gu workload should guarantee NUMA-aligned cpu cores in gu pods with single pod, multiple containers requesting 1 core, 1 device each [Serial][sig-node][Feature:TopologyManager] Configured cluster with gu workload should guarantee NUMA-aligned cpu cores in gu pods with single pod, single container requesting 1 core, 1 device [Serial][sig-node][Feature:TopologyManager] Configured cluster with gu workload should guarantee NUMA-aligned cpu cores in gu pods with single pod, single container requesting 4 cores, 1 device
Last Closed: 2020-09-17 11:57:48 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 Devan Goodwin 2020-09-17 11:23:23 UTC 
test:
[Serial][sig-node][Feature:TopologyManager] Configured cluster with gu workload attached to SRIOV networks should let resource-aligned PODs have working SRIOV network interface 

is failing frequently in CI, see search results:
https://search.ci.openshift.org/?maxAge=168h&context=1&type=bug%2Bjunit&name=&maxMatches=5&maxBytes=20971520&groupBy=job&search=%5C%5BSerial%5C%5D%5C%5Bsig-node%5C%5D%5C%5BFeature%3ATopologyManager%5C%5D+Configured+cluster+with+gu+workload+attached+to+SRIOV+networks+should+let+resource-aligned+PODs+have+working+SRIOV+network+interface


Sample failing job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/release-openshift-ocp-installer-e2e-openstack-serial-4.6/1306000862161670144

fail [github.com/openshift/origin/test/extended/topology_manager/utils.go:96]: Unexpected error:
    <*util.ExitError | 0xc0029ac9f0>: {
        Cmd: "oc --kubeconfig=/tmp/admin.kubeconfig rsh -n openshift-machine-config-operator -c machine-config-daemon --request-timeout 30 machine-config-daemon-w5zn9 cat /rootfs/etc/kubernetes/kubelet.conf",
        StdErr: "oc: /lib64/libc.so.6: version `GLIBC_2.28' not found (required by oc)",
        ExitError: {
            ProcessState: {
                pid: 2592,
                status: 256,
                rusage: {
                    Utime: {Sec: 0, Usec: 0},
                    Stime: {Sec: 0, Usec: 5144},
                    Maxrss: 81172,
                    Ixrss: 0,
                    Idrss: 0,
                    Isrss: 0,
                    Minflt: 62,
                    Majflt: 0,
                    Nswap: 0,
                    Inblock: 0,
                    Oublock: 0,
                    Msgsnd: 0,
                    Msgrcv: 0,
                    Nsignals: 0,
                    Nvcsw: 1,
                    Nivcsw: 1,
                },
            },
            Stderr: nil,
        },
    }
    exit status 1
occurred
Comment 1 Devan Goodwin 2020-09-17 11:29:49 UTC 
Adding multiple gu tests to environment.
Comment 2 Devan Goodwin 2020-09-17 11:57:48 UTC 

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