Description of problem: a specific test fails to capture this leading to false negatives The existing regression test which wants to cover against regressions on RHBZ#1813567 is actually doing the reverse check than it should. We noticed after having the test run for few days on environment kindly provided by nfvpe team. The likely cause of why this mistake sneaked in is that I wrongly configured the original environment on which I tried the test. This patch fixes the issue and puts extra care in documenting and checking the intent of the original bugzilla. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Verified on master branch of https://github.com/openshift/origin.git # git log -1 commit 3b3a17d295c52bb6712eaeea2682e682524b83cc (HEAD -> master, origin/release-4.7, origin/master, origin/HEAD) Merge: e8c19e8132 5703c585d5 Author: OpenShift Merge Robot <openshift-merge-robot.github.com> Date: Thu Oct 8 00:50:59 2020 -0400 Merge pull request #25583 from multi-arch/master hello-openshift: fix base images OCP 4.6.0-0.nightly-2020-10-03-051134 started: (0/6/11) "[Serial][sig-node][Feature:TopologyManager] Configured cluster with gu workload saturating NUMA nodes should guarantee correct allocation with concurrent creation [Suite:openshift/conformance/serial]" passed: (1m0s) 2020-10-08T15:13:00 "[Serial][sig-node][Feature:TopologyManager] Configured cluster with gu workload saturating NUMA nodes should guarantee correct allocation with concurrent creation [Suite:openshift/conformance/serial]"
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.6 GA Images), 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-2020:4196