openshift-ci-robot
commented
2 weeks ago @mrniranjan: This pull request references Jira Issue OCPBUGS-39379, which is valid. The bug has been moved to the POST state.
7 validation(s) were run on this bug
* bug is open, matching expected state (open) * bug target version (4.16.z) matches configured target version for branch (4.16.z) * bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST) * release note type set to "Release Note Not Required" * dependent bug [Jira Issue OCPBUGS-39127](https://issues.redhat.com//browse/OCPBUGS-39127) is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA)) * dependent [Jira Issue OCPBUGS-39127](https://issues.redhat.com//browse/OCPBUGS-39127) targets the "4.17.0" version, which is one of the valid target versions: 4.17.0 * bug has dependentsRequesting review from QA contact: /cc @mrniranjan
The bug has been updated to refer to the pull request using the external bug tracker.
In response to [this](https://github.com/openshift/cluster-node-tuning-operator/pull/1153):
>Automates OCPBUGS-34812: cgroupsv2: failed to write on cpuset.cpus.exclusive
>
>To reproduce the bug, we need to create and delete deployment(deploying guaranteed pods with cpu load balancing annotation) in quick succession, so that we do not fully wait for the cleanup causing the pod about to be deleted to still have access to exclusive cpus causing the new pod to fail because cpuset.cpus.exclusive is not yet freed.
>
>As the pre-start hook fails to write to cpuset.cpus.exclusive file in the pods cgroup pod goes to RunContainerError state.
>
>This automation PR creates and deletes deployment in loop to reproduce the issue and checks if the pods fails with Runtime error with message "failed to run pre-start hook for container"
>
>Manual backport of PR#1127
Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fcluster-node-tuning-operator). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.
openshift-ci[bot]
yanirq
mrniranjan
Automates OCPBUGS-34812: cgroupsv2: failed to write on cpuset.cpus.exclusive
To reproduce the bug, we need to create and delete deployment(deploying guaranteed pods with cpu load balancing annotation) in quick succession, so that we do not fully wait for the cleanup causing the pod about to be deleted to still have access to exclusive cpus causing the new pod to fail because cpuset.cpus.exclusive is not yet freed.
As the pre-start hook fails to write to cpuset.cpus.exclusive file in the pods cgroup pod goes to RunContainerError state.
This automation PR creates and deletes deployment in loop to reproduce the issue and checks if the pods fails with Runtime error with message "failed to run pre-start hook for container"
Manual backport of #1127