-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Add canary job for installer w/ OpenStack #4712
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
Add canary job for installer w/ OpenStack #4712
Conversation
|
if you add it like other canary https://github.com/openshift/release/blob/master/ci-operator/jobs/openshift/release/openshift-release-release-4.2-periodics.yaml you might be able to get it into the canary dashboard. |
6090977 to
bb46a9c
Compare
Thanks, I've updated the PR to target the 4.2 periodics |
|
/lgtm |
|
/lgtm |
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.
This would normally be a release periodic, we put them together so you can track. Search for "canary-*" and you should see a bunch of canary-release-* jobs. Move this into there and give it consistent names.
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.
Sorry, I see you have a periodic here. Basically if you have a release periodic you shouldn't do a post submit. It'll show the same info but in a confusing way.
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 intended to remove that from the last rebase (my first attempt here). Let me get rid of the post-commit job and just leave the periodic(canary) job.
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.
How long until this is fixed to run all e2e tests?
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.
Following up on your question about tests this afternoon. The answer is I think we can try them now. The reason we ran minimal for some of the openstack pre/post submit jobs I think was solely to save time on those jobs.
|
Two comments, looks fine otherwise |
bb46a9c to
0c94356
Compare
I think I got them both address in this last rebase. Thanks |
ci-operator/jobs/openshift/release/openshift-release-release-4.2-periodics.yaml
Outdated
Show resolved
Hide resolved
|
/test pj-rehearse |
|
Please set the rehearsal label so you get feedback here: |
|
Yeah, want to see rehearsal. |
0c94356 to
1c60dea
Compare
|
/test pj-rehearse |
ci-operator/jobs/openshift/release/openshift-release-release-4.2-periodics.yaml
Outdated
Show resolved
Hide resolved
|
/test pj-rehearse |
79baf41 to
41b2126
Compare
|
/test pj-rehearse |
|
The bootkube.log on the bootstrap has this: Error reading manifest 4.2 in registry.svc.ci.openshift.org/ocp/release: unauthorized: authentication required. Maybe we need another pull-secret? |
41b2126 to
45c085c
Compare
|
/test pj-rehearse |
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.
Hmm, the usual OpenStack presubmit only has the profile secret. I don't understand how that works, but it seems like it does. Maybe try to get closer to that template, or try to get @flaper87 to explain why he didn't need the pull-secret entry in #1824?
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.
Could be related to the old "inline" nature of the secrets. I pushed this to align OpenStack with the latest attachements: #4823
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.
One more observation would be what you said above applies to all the AWS jobs too. OpenStack is working in presubmit, yes! But it seems like the Canary jobs should align as well.
|
/test pj-rehearse |
1 similar comment
|
/test pj-rehearse |
6bf1a07 to
86f3035
Compare
|
/test pj-rehearse |
86f3035 to
412a386
Compare
|
/test pj-rehearse |
|
Just got word that the CI secrets for OpenStack jobs have been updated. They should now contain a registry key for "registry.connect.redhat.com", "registry.redhat.io", and "registry.svc.ci.openshift.org". So now maybe this has a chance to pass. |
|
/test pj-rehearse |
4 similar comments
|
/test pj-rehearse |
|
/test pj-rehearse |
|
/test pj-rehearse |
|
/test pj-rehearse |
|
@dprince: The following tests failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. DetailsInstructions 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/test-infra repository. I understand the commands that are listed here. |
|
The OpenStack job is now running. As we've enabled all the tests there are some failures there but this job should be ready to land now I think. |
|
/lgtm |
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dprince, eparis, iamemilio, stevekuznetsov, wking The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
@dprince: Updated the
DetailsIn 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 kubernetes/test-infra repository. |
No description provided.