Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MON-3848: add e2e-aws-ovn-single-node techpreview jobs #51509

Merged
merged 1 commit into from
May 29, 2024

Conversation

machine424
Copy link
Contributor

No description provided.

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

openshift-ci-robot commented Apr 30, 2024

@machine424: This pull request references MON-3848 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.16.0" version, but no target version was set.

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.

@machine424
Copy link
Contributor Author

/pj-rehearse

@openshift-ci-robot
Copy link
Contributor

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

Copy link
Contributor

openshift-ci bot commented May 3, 2024

@machine424: the repo openshift/release does not contribute to the OpenShift official images

1 similar comment
Copy link
Contributor

openshift-ci bot commented May 3, 2024

@machine424: the repo openshift/release does not contribute to the OpenShift official images

@machine424
Copy link
Contributor Author

/payload-job-with-prs periodic-ci-openshift-release-master-nightly-4.16-e2e-aws-ovn-single-node-techpreview openshift/cluster-monitoring-operator#2334 openshift/kubernetes-metrics-server#26 openshift/kubernetes#1960 openshift/machine-config-operator#4338

Copy link
Contributor

openshift-ci bot commented May 3, 2024

@machine424: the repo openshift/release does not contribute to the OpenShift official images

@machine424
Copy link
Contributor Author

/pj-rehearse

@openshift-ci-robot
Copy link
Contributor

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

@machine424
Copy link
Contributor Author

/pj-rehearse

@openshift-ci-robot
Copy link
Contributor

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

@@ -138,6 +138,20 @@
"name": "periodic-ci-openshift-release-master-nightly-4.16-e2e-aws-ovn-single-node-serial-priv"
}
},
"aws-ovn-single-node-techpreview": {
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I had to add those priv entries, where are they used?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@bradmwilliams Would know for sure, but I think it had to do with CVE validation in the private environments by adding the -priv suffix.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You should only ever modify the files in: core-services/release-controller/_releases and then run a make release-controllers to automatically generate the files in: core-services/release-controller/_releases/priv.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, I've run make release-controllers as requested in the error message
I just wanted to know more about those priv jobs.

@machine424
Copy link
Contributor Author

/pj-rehearse periodic-ci-openshift-release-master-nightly-4.17-e2e-aws-ovn-single-node-techpreview periodic-ci-openshift-release-master-nightly-4.16-e2e-aws-ovn-single-node-techpreview

/retest

@openshift-ci-robot
Copy link
Contributor

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

@openshift-ci-robot
Copy link
Contributor

[REHEARSALNOTIFIER]
@machine424: the pj-rehearse plugin accommodates running rehearsal tests for the changes in this PR. Expand 'Interacting with pj-rehearse' for usage details. The following rehearsable tests have been affected by this change:

Test name Repo Type Reason
periodic-ci-openshift-release-master-nightly-4.16-e2e-aws-ovn-single-node-techpreview N/A periodic Periodic changed
periodic-ci-openshift-release-master-nightly-4.17-e2e-aws-ovn-single-node-techpreview-serial N/A periodic Periodic changed
periodic-ci-openshift-release-master-nightly-4.17-e2e-aws-ovn-single-node-techpreview N/A periodic Periodic changed
periodic-ci-openshift-release-master-nightly-4.16-e2e-aws-ovn-single-node-techpreview-serial N/A periodic Periodic changed
Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse abort to abort all active rehearsals

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

@machine424
Copy link
Contributor Author

/pj-rehearse periodic-ci-openshift-release-master-nightly-4.17-e2e-aws-ovn-single-node-techpreview periodic-ci-openshift-release-master-nightly-4.16-e2e-aws-ovn-single-node-techpreview

@openshift-ci-robot
Copy link
Contributor

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

@machine424
Copy link
Contributor Author

/pj-rehearse periodic-ci-openshift-release-master-nightly-4.17-e2e-aws-ovn-single-node-techpreview periodic-ci-openshift-release-master-nightly-4.16-e2e-aws-ovn-single-node-techpreview

@openshift-ci-robot
Copy link
Contributor

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

@slashpai
Copy link
Member

/pj-rehearse periodic-ci-openshift-release-master-nightly-4.16-e2e-aws-ovn-single-node-techpreview

@openshift-ci-robot
Copy link
Contributor

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

@eggfoobar
Copy link
Contributor

/pj-rehearse periodic-ci-openshift-release-master-nightly-4.16-e2e-aws-ovn-single-node-techpreview

Retrying job, that failure is odd and I'm investigating why that failed to install, but it seems like an install fluke.

@openshift-ci-robot
Copy link
Contributor

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

@eggfoobar
Copy link
Contributor

/pj-rehearse periodic-ci-openshift-release-master-nightly-4.16-e2e-aws-ovn-single-node-techpreview

@openshift-ci-robot
Copy link
Contributor

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

@slashpai
Copy link
Member

/pj-rehearse periodic-ci-openshift-release-master-nightly-4.16-e2e-aws-ovn-single-node-techpreview

@openshift-ci-robot
Copy link
Contributor

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

@eggfoobar
Copy link
Contributor

/pj-rehearse periodic-ci-openshift-release-master-nightly-4.16-e2e-aws-ovn-single-node-techpreview-serial periodic-ci-openshift-release-master-nightly-4.17-e2e-aws-ovn-single-node-techpreview-serial

Fix for serial should be in latest nightly, trying

@openshift-ci-robot
Copy link
Contributor

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

@eggfoobar
Copy link
Contributor

/pj-rehearse periodic-ci-openshift-release-master-nightly-4.16-e2e-aws-ovn-single-node-techpreview-serial periodic-ci-openshift-release-master-nightly-4.17-e2e-aws-ovn-single-node-techpreview-serial

@openshift-ci-robot
Copy link
Contributor

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

@eggfoobar
Copy link
Contributor

We're currently getting hit by a known bug in the CAPI install for AWS, we'll wait on retrying serial until that is resolved.

Copy link
Contributor

openshift-ci bot commented May 20, 2024

@machine424: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/rehearse/periodic-ci-openshift-release-master-nightly-4.16-e2e-aws-ovn-single-node-techpreview-serial 91a01d2 link unknown /pj-rehearse periodic-ci-openshift-release-master-nightly-4.16-e2e-aws-ovn-single-node-techpreview-serial

Full PR test history. Your PR dashboard.

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.

@eggfoobar
Copy link
Contributor

/lgtm

This looks good, 4.17 shows the skip happening

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label May 20, 2024
@stbenjam
Copy link
Member

/approve

Copy link
Contributor

openshift-ci bot commented May 29, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: eggfoobar, machine424, stbenjam

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:

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 May 29, 2024
@eggfoobar
Copy link
Contributor

/pj-rehearse ack

@openshift-ci-robot
Copy link
Contributor

@eggfoobar: 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 May 29, 2024
@openshift-merge-bot openshift-merge-bot bot merged commit 8321158 into openshift:master May 29, 2024
21 of 23 checks passed
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
6 participants