Skip to content

USHIFT-3501: separate periodic upgrade tests to reduce resource pressure on hypervisor#3506

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:mainfrom
copejon:ushift-3501
Jun 19, 2024
Merged

USHIFT-3501: separate periodic upgrade tests to reduce resource pressure on hypervisor#3506
openshift-merge-bot[bot] merged 1 commit intoopenshift:mainfrom
copejon:ushift-3501

Conversation

@copejon
Copy link
Copy Markdown
Contributor

@copejon copejon commented Jun 18, 2024

This PR handles the changes required in the microshift repo. A PR in openshift/release will create a new parallel job to execute these scenarios on

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

openshift-ci-robot commented Jun 18, 2024

@copejon: This pull request references USHIFT-3501 which is a valid jira issue.

Details

In response to this:

This PR handles the changes required in the microshift repo. A PR in openshift/release will create a new parallel job to execute these scenarios on

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.

@copejon
Copy link
Copy Markdown
Contributor Author

copejon commented Jun 18, 2024

/cherry-pick release-4.16

@openshift-cherrypick-robot
Copy link
Copy Markdown

@copejon: once the present PR merges, I will cherry-pick it on top of release-4.16 in a new PR and assign it to you.

Details

In response to this:

/cherry-pick release-4.16

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.

@openshift-ci openshift-ci bot requested review from ggiguash and pacevedom June 18, 2024 16:47
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 18, 2024
@ggiguash
Copy link
Copy Markdown
Contributor

@copejon , can we use scenarios-upgrades directory name? The fact that it's run in periodics should not be reflected in the dir name.

… resource pressure on the hypervisor hosts in CI, which was causing greenboot timeouts

Signed-off-by: Jon Cope <jcope@redhat.com>
@ggiguash
Copy link
Copy Markdown
Contributor

/lgtm

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

openshift-ci bot commented Jun 19, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: copejon, ggiguash

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-robot
Copy link
Copy Markdown

/retest-required

Remaining retests: 0 against base HEAD e9533cf and 2 for PR HEAD d48ac06 in total

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Jun 19, 2024

@copejon: 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.

@openshift-cherrypick-robot
Copy link
Copy Markdown

@copejon: new pull request created: #3512

Details

In response to this:

/cherry-pick release-4.16

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.

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.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants