Skip to content

OCPNODE-4037: Add periodic job for openshift long running test suite#74043

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:mainfrom
ngopalak-redhat:ngopalak/node-long-running1
Feb 11, 2026
Merged

OCPNODE-4037: Add periodic job for openshift long running test suite#74043
openshift-merge-bot[bot] merged 1 commit intoopenshift:mainfrom
ngopalak-redhat:ngopalak/node-long-running1

Conversation

@ngopalak-redhat
Copy link
Copy Markdown
Contributor

@ngopalak-redhat ngopalak-redhat commented Jan 28, 2026

The PR adds a periodic job that runs once in 24 hours.
Its configured to be informing
The test was added in openshift/origin#30648
I have done a pj-rehearse and the results are available here:
https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/openshift_release/74043/rehearse-74043-periodic-ci-openshift-release-main-nightly-4.22-e2e-aws-disruptive-longrunning/2021023730955718656


: [Suite:openshift/disruptive-longrunning][sig-node][Disruptive] [Slow]should apply KubeletConfig with logging verbosity to custom pool [apigroup:machineconfiguration.openshift.io] [Serial] | 5m21s
-- | --


More tests will be added to this periodic run. For example AutoNodeSizing, system-compressible etc. These tests generally take more than 5 mins to run.

@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jan 28, 2026
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Jan 28, 2026

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@ngopalak-redhat
Copy link
Copy Markdown
Contributor Author

/test all

@ngopalak-redhat ngopalak-redhat force-pushed the ngopalak/node-long-running1 branch from 8991ca5 to 9cf5cd3 Compare January 28, 2026 04:26
@ngopalak-redhat
Copy link
Copy Markdown
Contributor Author

/retest-required

@ngopalak-redhat ngopalak-redhat force-pushed the ngopalak/node-long-running1 branch from 9cf5cd3 to 12fd28e Compare January 28, 2026 07:48
@ngopalak-redhat
Copy link
Copy Markdown
Contributor Author

/retest-required

@ngopalak-redhat ngopalak-redhat force-pushed the ngopalak/node-long-running1 branch from 12fd28e to c896e62 Compare January 28, 2026 08:42
@ngopalak-redhat
Copy link
Copy Markdown
Contributor Author

/retest-required

@ngopalak-redhat ngopalak-redhat force-pushed the ngopalak/node-long-running1 branch from c896e62 to 2c3f95a Compare January 28, 2026 09:17
@ngopalak-redhat
Copy link
Copy Markdown
Contributor Author

/retest-required

@ngopalak-redhat
Copy link
Copy Markdown
Contributor Author

/pj-rehearse periodic-ci-openshift-origin-release-4.23-e2e-aws-disruptive-longrunning

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@ngopalak-redhat: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@ngopalak-redhat ngopalak-redhat force-pushed the ngopalak/node-long-running1 branch from 2c3f95a to e4c34c3 Compare January 28, 2026 15:39
@ngopalak-redhat
Copy link
Copy Markdown
Contributor Author

/retest-required

@ngopalak-redhat
Copy link
Copy Markdown
Contributor Author

/pj-rehearse periodic-ci-openshift-origin-release-4.23-e2e-aws-disruptive-longrunning

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@ngopalak-redhat: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@ngopalak-redhat ngopalak-redhat changed the title Add periodic job for openshift long running test suite OCPNODE-4037: Add periodic job for openshift long running test suite Jan 29, 2026
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

openshift-ci-robot commented Jan 29, 2026

@ngopalak-redhat: This pull request references OCPNODE-4037 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.22.0" version, but no target version was set.

Details

In response to this:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jan 29, 2026
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

openshift-ci-robot commented Jan 29, 2026

@ngopalak-redhat: This pull request references OCPNODE-4037 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.22.0" version, but no target version was set.

Details

In response to this:

The PR adds a periodic job that runs once in 24 hours.
Its configured to be informing
The test was added in openshift/origin#30648

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

openshift-ci-robot commented Jan 29, 2026

@ngopalak-redhat: This pull request references OCPNODE-4037 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.22.0" version, but no target version was set.

Details

In response to this:

The PR adds a periodic job that runs once in 24 hours.
Its configured to be informing
The test was added in openshift/origin#30648
I have done a pj-rehearse and the results are available here: https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/openshift_release/74043/rehearse-74043-periodic-ci-openshift-origin-release-4.23-e2e-aws-disruptive-longrunning/2016670789008363520

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

openshift-ci-robot commented Jan 29, 2026

@ngopalak-redhat: This pull request references OCPNODE-4037 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.22.0" version, but no target version was set.

Details

In response to this:

The PR adds a periodic job that runs once in 24 hours.
Its configured to be informing
The test was added in openshift/origin#30648
I have done a pj-rehearse and the results are available here: https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/openshift_release/74043/rehearse-74043-periodic-ci-openshift-origin-release-4.23-e2e-aws-disruptive-longrunning/2016670789008363520
More tests will be added to this periodic run. For example AutoNodeSizing, system-compressible etc. These tests generally take more than 5 mins to run.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@ngopalak-redhat
Copy link
Copy Markdown
Contributor Author

/pj-rehearse ack

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@ngopalak-redhat: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@openshift-ci-robot openshift-ci-robot added the rehearsals-ack Signifies that rehearsal jobs have been acknowledged label Jan 29, 2026
@ngopalak-redhat ngopalak-redhat marked this pull request as ready for review January 29, 2026 03:23
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jan 29, 2026
@ngopalak-redhat
Copy link
Copy Markdown
Contributor Author

/assign @cpmeadors

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Feb 11, 2026

@ngopalak-redhat: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@ngopalak-redhat
Copy link
Copy Markdown
Contributor Author

/pj-rehearse ack


[Suite:openshift/disruptive-longrunning][sig-node][Disruptive] [Slow]should apply KubeletConfig with logging verbosity to custom pool [apigroup:machineconfiguration.openshift.io] [Serial] | 6m58s
-- | --

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@ngopalak-redhat: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@openshift-ci-robot openshift-ci-robot added the rehearsals-ack Signifies that rehearsal jobs have been acknowledged label Feb 11, 2026
@neisw
Copy link
Copy Markdown
Contributor

neisw commented Feb 11, 2026

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 11, 2026
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Feb 11, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cpmeadors, neisw, ngopalak-redhat

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

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 11, 2026
@openshift-merge-bot openshift-merge-bot bot merged commit 2032f23 into openshift:main Feb 11, 2026
16 checks passed
gpei pushed a commit to gpei/release that referenced this pull request Feb 18, 2026
memodi pushed a commit to memodi/release that referenced this pull request Feb 18, 2026
theautoroboto pushed a commit to theautoroboto/release that referenced this pull request Feb 19, 2026
dhensel-rh pushed a commit to dhensel-rh/release that referenced this pull request Feb 19, 2026
rrasouli pushed a commit to rrasouli/release that referenced this pull request Mar 3, 2026
kannon92 pushed a commit to kannon92/release that referenced this pull request Mar 3, 2026
wangke19 pushed a commit to wangke19/release that referenced this pull request Mar 4, 2026
rrasouli pushed a commit to rrasouli/release that referenced this pull request Mar 5, 2026
weinliu pushed a commit to weinliu/release that referenced this pull request Mar 6, 2026
sdodson pushed a commit to sdodson/release that referenced this pull request Mar 8, 2026
kasturinarra pushed a commit to kasturinarra/release that referenced this pull request Mar 11, 2026
tareqalayan pushed a commit to tareqalayan/release that referenced this pull request Mar 13, 2026
qiliRedHat pushed a commit to qiliRedHat/release that referenced this pull request Mar 13, 2026
MayXuQQ pushed a commit to MayXuQQ/release that referenced this pull request Mar 17, 2026
kasturinarra pushed a commit to kasturinarra/release that referenced this pull request Mar 17, 2026
sairameshv pushed a commit to sairameshv/release that referenced this pull request Mar 23, 2026
zhouying7780 pushed a commit to zhouying7780/release that referenced this pull request Mar 25, 2026
rrasouli pushed a commit to rrasouli/release that referenced this pull request Mar 25, 2026
anpingli pushed a commit to anpingli/release that referenced this pull request Mar 30, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. rehearsals-ack Signifies that rehearsal jobs have been acknowledged

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants