search

openshift / cluster-node-tuning-operator

Manage node-level tuning by orchestrating the tuned daemon.
Apache License 2.0
99 stars 104 forks source link

[release-4.17] OCPBUGS-41330: E2E: wait for ovs services affinity to reset after deployment deletion #1160

Open openshift-cherrypick-robot opened 1 week ago

openshift-cherrypick-robot commented 1 week ago

This is an automated cherry-pick of #1158

/assign mrniranjan

openshift-ci-robot commented 1 week ago

@openshift-cherrypick-robot: Jira Issue OCPBUGS-41329 has been cloned as Jira Issue OCPBUGS-41330. Will retitle bug to link to clone. /retitle [release-4.17] OCPBUGS-41330: E2E: wait for ovs services affinity to reset after deployment deletion

In response to [this](https://github.com/openshift/cluster-node-tuning-operator/pull/1160): >This is an automated cherry-pick of #1158 > >/assign mrniranjan 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-robot commented 1 week ago

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-41330, 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.17.0) matches configured target version for branch (4.17.0) * 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-41329](https://issues.redhat.com//browse/OCPBUGS-41329) is in the state MODIFIED, which is one of the valid states (MODIFIED, ON_QA, VERIFIED) * dependent [Jira Issue OCPBUGS-41329](https://issues.redhat.com//browse/OCPBUGS-41329) targets the "4.18.0" version, which is one of the valid target versions: 4.18.0 * bug has dependents

Requesting review from QA contact: /cc @gsr-shanks

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/1160): >This is an automated cherry-pick of #1158 > >/assign mrniranjan 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.
mrniranjan commented 1 week ago

/test e2e-gcp-pao-workloadhints

openshift-ci[bot] commented 1 week ago

@openshift-cherrypick-robot: all tests passed!

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository. I understand the commands that are listed [here](https://go.k8s.io/bot-commands).
yanirq commented 1 week ago

/approve /label backport-risk-assessed

openshift-ci[bot] commented 1 week ago

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: openshift-cherrypick-robot, yanirq

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files: - ~~[OWNERS](https://github.com/openshift/cluster-node-tuning-operator/blob/release-4.17/OWNERS)~~ [yanirq] Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment