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

OCPBUGS-31690: [manual][release-4.15] E2E: Reduce number of reboots in offline tests #1014

Closed mrniranjan closed 7 months ago

mrniranjan commented 7 months ago

OCPBUGS-29594: Reduce number of reboots in offline tests (#940)

Currently in offline tests we rever to original profile after each tests, this is very costly and causing tests to run for long time.

This patch addresses by reverting to the profile after all offline tests are run.

openshift-ci-robot commented 7 months ago

@mrniranjan: This pull request references Jira Issue OCPBUGS-31687, which is invalid:

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/1014): >OCPBUGS-29594: Reduce number of reboots in offline tests (#940) > >* Reduce number of reboots in offline tests > >Currently in offline tests we rever to original profile after each tests, this is very costly and causing tests to run for long time. > >This patch addresses by reverting to the profile after all offline tests are run. 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 7 months ago

@mrniranjan: No Jira issue is referenced in the title of this pull request. To reference a jira issue, add 'XYZ-NNN:' to the title of this pull request and request another refresh with /jira refresh.

In response to [this](https://github.com/openshift/cluster-node-tuning-operator/pull/1014): >OCPBUGS-29594: Reduce number of reboots in offline tests (#940) > >* Reduce number of reboots in offline tests > >Currently in offline tests we rever to original profile after each tests, this is very costly and causing tests to run for long time. > >This patch addresses by reverting to the profile after all offline tests are run. 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 7 months ago

@mrniranjan: This pull request references Jira Issue OCPBUGS-31690, which is invalid:

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/1014): >OCPBUGS-29594: Reduce number of reboots in offline tests (#940) > >* Reduce number of reboots in offline tests > >Currently in offline tests we rever to original profile after each tests, this is very costly and causing tests to run for long time. > >This patch addresses by reverting to the profile after all offline tests are run. 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 7 months ago

/jira refresh

openshift-ci-robot commented 7 months ago

@mrniranjan: This pull request references Jira Issue OCPBUGS-31690, 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.z) matches configured target version for branch (4.15.z) * bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST) * dependent bug [Jira Issue OCPBUGS-29595](https://issues.redhat.com//browse/OCPBUGS-29595) 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-29595](https://issues.redhat.com//browse/OCPBUGS-29595) 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 (mniranja@redhat.com), skipping review request.

In response to [this](https://github.com/openshift/cluster-node-tuning-operator/pull/1014#issuecomment-2034300343): >/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.
mrniranjan commented 7 months ago

/test e2e-gcp-pao-updating-profile

openshift-ci[bot] commented 7 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/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
mrniranjan commented 7 months ago

/label cherry-pick-approved

yanirq commented 7 months ago

/label backport-risk-assessed

openshift-ci-robot commented 7 months ago

/retest-required

Remaining retests: 0 against base HEAD e0ab1c161e8c61ae0f10ba954b2958f5054feee9 and 2 for PR HEAD 0a3536b9d80d1a366ccd8340005fb806869a0d26 in total

mrniranjan commented 7 months ago

/test e2e-hypershift

yanirq commented 7 months ago

/retest-required

mrniranjan commented 7 months ago

/test e2e-hypershift

mrniranjan commented 7 months ago

/retest-required

mrniranjan commented 7 months ago

/test e2e-hypershift

mrniranjan commented 7 months ago

/test e2e-hypershift

openshift-ci[bot] commented 7 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/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 commented 7 months ago

@mrniranjan: Jira Issue OCPBUGS-31690: All pull requests linked via external trackers have merged:

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

In response to [this](https://github.com/openshift/cluster-node-tuning-operator/pull/1014): >OCPBUGS-29594: Reduce number of reboots in offline tests (#940) > >* Reduce number of reboots in offline tests > >Currently in offline tests we rever to original profile after each tests, this is very costly and causing tests to run for long time. > >This patch addresses by reverting to the profile after all offline tests are run. 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 commented 7 months ago

[ART PR BUILD NOTIFIER]

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

mrniranjan commented 7 months ago

/cherry-pick release-4.14

openshift-cherrypick-robot commented 7 months ago

@mrniranjan: new pull request created: #1035

In response to [this](https://github.com/openshift/cluster-node-tuning-operator/pull/1014#issuecomment-2054265397): >/cherry-pick release-4.14 > > 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.
mrniranjan commented 7 months ago

/cherry-pick release-4.14

openshift-cherrypick-robot commented 7 months ago

@mrniranjan: new pull request could not be created: failed to create pull request against openshift/cluster-node-tuning-operator#release-4.14 from head openshift-cherrypick-robot:cherry-pick-1014-to-release-4.14: status code 422 not one of [201], body: {"message":"Validation Failed","errors":[{"resource":"PullRequest","code":"custom","message":"A pull request already exists for openshift-cherrypick-robot:cherry-pick-1014-to-release-4.14."}],"documentation_url":"https://docs.github.com/rest/pulls/pulls#create-a-pull-request"}

In response to [this](https://github.com/openshift/cluster-node-tuning-operator/pull/1014#issuecomment-2071573845): >/cherry-pick release-4.14 > > 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.
mrniranjan commented 7 months ago

/cherry-pick release-4.13