[release-4.15][manual] OCPBUGS-29396: Labels for e2e testing

[Tal-or]

backport of:

• https://github.com/openshift/cluster-node-tuning-operator/pull/947
• https://github.com/openshift/cluster-node-tuning-operator/pull/936

[openshift-ci-robot]

@Tal-or: This pull request explicitly references no jira issue.

In response to [this](https://github.com/openshift/cluster-node-tuning-operator/pull/949): >backport of: >* https://github.com/openshift/cluster-node-tuning-operator/pull/947 >* https://github.com/openshift/cluster-node-tuning-operator/pull/936 > 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.

[Tal-or]

/cc @mrniranjan @ffromani

[openshift-ci[bot]]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ffromani, Tal-or

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.15/OWNERS)~~ [ffromani] Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment

[yanirq]

/label backport-risk-assessed

[shajmakh]

/label cherry-pick-approved

[Tal-or]

/retest

[openshift-ci-robot]

@Tal-or: This pull request references Jira Issue OCPBUGS-29396, which is invalid:

• expected the bug to target the "4.15.0" version, but no target version was set
• expected dependent Jira Issue OCPBUGS-29395 to target a version in 4.16.0, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

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/949): >backport of: >* https://github.com/openshift/cluster-node-tuning-operator/pull/947 >* https://github.com/openshift/cluster-node-tuning-operator/pull/936 > 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.

[Tal-or]

/jira refresh

[openshift-ci-robot]

@Tal-or: This pull request references Jira Issue OCPBUGS-29396, which is valid. The bug has been moved to the POST state.

6 validation(s) were run on this bug

* bug is open, matching expected state (open) * bug target version (4.15.0) matches configured target version for branch (4.15.0) * bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST) * dependent bug [Jira Issue OCPBUGS-29395](https://issues.redhat.com//browse/OCPBUGS-29395) is in the state Verified, which is one of the valid states (MODIFIED, ON_QA, VERIFIED) * dependent [Jira Issue OCPBUGS-29395](https://issues.redhat.com//browse/OCPBUGS-29395) targets the "4.16.0" version, which is one of the valid target versions: 4.16.0 * bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira (liqcui@redhat.com), skipping review request.

In response to [this](https://github.com/openshift/cluster-node-tuning-operator/pull/949#issuecomment-1940662874): >/jira refresh 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.

[Tal-or]

/retest This PR cannot affect any of the test since it's an API proposal which not being used yet.

[openshift-ci[bot]]

@Tal-or: 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/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository. I understand the commands that are listed [here](https://go.k8s.io/bot-commands).

[openshift-ci-robot]

@Tal-or: Jira Issue OCPBUGS-29396: All pull requests linked via external trackers have merged:

• openshift/cluster-node-tuning-operator#949

Jira Issue OCPBUGS-29396 has been moved to the MODIFIED state.

In response to [this](https://github.com/openshift/cluster-node-tuning-operator/pull/949): >backport of: >* https://github.com/openshift/cluster-node-tuning-operator/pull/947 >* https://github.com/openshift/cluster-node-tuning-operator/pull/936 > 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-bot]

[ART PR BUILD NOTIFIER]

This PR has been included in build cluster-node-tuning-operator-container-v4.15.0-202402131237.p0.gc2c52f6.assembly.stream.el9 for distgit cluster-node-tuning-operator. All builds following this will include this PR.

[openshift-merge-robot]

Fix included in accepted release 4.15.0-0.nightly-2024-02-13-161104