search

openshift / cluster-node-tuning-operator

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

NO-JIRA: E2E: Fetch pod node instead of relying on first worker-cnf node #1070

Closed mrniranjan closed 5 months ago

mrniranjan commented 5 months ago

When tests are executed on multiple worker-cnf nodes the guaranteed pod with crio annotations can be scheduled on any node. We fetch the node on which pod is running and check load balancing on that target node

openshift-ci-robot commented 5 months ago

@mrniranjan: This pull request explicitly references no jira issue.

In response to [this](https://github.com/openshift/cluster-node-tuning-operator/pull/1070): >When tests are executed on multiple worker-cnf nodes the guaranteed pod with crio annotations can be scheduled on any node. We fetch the node on which pod is running and check load balancing on that target node 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.
ffromani commented 5 months ago

/approve

openshift-ci[bot] commented 5 months ago

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ffromani, mrniranjan

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/master/OWNERS)~~ [ffromani] Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment
mrniranjan commented 5 months ago

/retest-required

mrniranjan commented 5 months ago

/retest-required

yanirq commented 5 months ago

/retest

yanirq commented 5 months ago

/lgtm

openshift-ci-robot commented 5 months ago

/retest-required

Remaining retests: 0 against base HEAD 03f4259768118dd3c8b2d5f027f405acb27cdffb and 2 for PR HEAD 32021d217df3bf9d2bb3e94daebb38df55463cea in total

mrniranjan commented 5 months ago

/retest-required

mrniranjan commented 5 months ago

/retest-required

openshift-ci[bot] commented 5 months ago

@mrniranjan: 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).
openshift-bot commented 5 months ago

[ART PR BUILD NOTIFIER]

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