-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Conversation
@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. |
/pj-rehearse |
@machine424: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
@machine424: the repo openshift/release does not contribute to the OpenShift official images |
1 similar comment
@machine424: the repo openshift/release does not contribute to the OpenShift official images |
/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 |
@machine424: the repo openshift/release does not contribute to the OpenShift official images |
/pj-rehearse |
@machine424: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
/pj-rehearse |
@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": { |
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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
.
There was a problem hiding this comment.
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.
/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 |
@machine424: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
make them "informing".
[REHEARSALNOTIFIER]
Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
/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 |
@machine424: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
/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 |
@machine424: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
/pj-rehearse periodic-ci-openshift-release-master-nightly-4.16-e2e-aws-ovn-single-node-techpreview |
@slashpai: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
/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. |
@eggfoobar: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
/pj-rehearse periodic-ci-openshift-release-master-nightly-4.16-e2e-aws-ovn-single-node-techpreview |
@eggfoobar: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
/pj-rehearse periodic-ci-openshift-release-master-nightly-4.16-e2e-aws-ovn-single-node-techpreview |
@slashpai: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
/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 |
@eggfoobar: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
/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 |
@eggfoobar: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
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. |
@machine424: The following test failed, say
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. |
/lgtm This looks good, 4.17 shows the skip happening |
/approve |
[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 |
/pj-rehearse ack |
@eggfoobar: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
8321158
into
openshift:master
No description provided.