-
Notifications
You must be signed in to change notification settings - Fork 4.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
remove oapi #21782
remove oapi #21782
Conversation
rebased and ready for review. I expect we'll bump through a few more tests |
/lgtm |
/retest Please review the full test history for this PR and help us cut down flakes. |
1 similar comment
/retest Please review the full test history for this PR and help us cut down flakes. |
bumped into containers/image#570 . I'll update our fork to unstick this pull to start. |
/retest Please review the full test history for this PR and help us cut down flakes. |
New changes are detected. LGTM label has been removed. |
@bparees is the e2e-aws-builds job currently in a good state? I may have missed a couple, but I thought I got everything under /test |
@bparees the e2e-aws-serial job |
as far as i know, other than occasional flakes until the longrunning behavior for instantiate binary is restored..I think you guys have a PR for that but i'm not sure it's merged? |
@deads2k you can ask @gabemontero about the pipeline test failures. i know he was fixing a flake but it's also possible the pipelines use oapi somewhere, up to and including the jenkins plugins themselves. |
looks like the test itself runs an image w/ skopeo in it so probably we need an updated version of skopeo that has whatever fix you've done to go against the right signatures api? |
@deads2k https://github.com/openshift/origin/blob/master/test/extended/testdata/signer-buildconfig.yaml#L21 and before you complaint to me about it: |
@bparees @deads2k the https://openshift-gce-devel.appspot.com/build/origin-ci-test/pr-logs/pull/21782/pull-ci-openshift-origin-master-e2e-aws-builds/454 failures were unrelated to the flake fix I hope to have merged Tuesday AM These failures were from the token ( The login plugin is using these uri's:
So yeah, seems like an oapi removal would have some impact. And I see 404's trying to hit those uri's in the jenkins log. So confirmed. |
@gabemontero thanks, we'll have to queue up fixing that before this can merge. Do any of the other jenkins plugins use oapi? |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: deads2k, mfojtik 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 |
FWIW that test could be updated at origin/test/extended/images/signatures.go Line 102 in 8fa6f2f
"docker://" instead of "atomic:" and it should continue to work (as long as the registry is ≥1.5.0-alpha.3); that would also allow removing the oc login call and the KUBERNETES_MASTER environment variable.
Of course none of this changes the fact that removing the namespace breaks all existing builds of |
/retest |
1 similar comment
/retest |
|
/test e2e-aws-builds |
So I'm guessing you need #21921 to land which picks up the new new containers in vendor. |
/retest |
I think gabe was seeing some slowness today, yes.. i just had a successful aws-builds job run on another PR, so let's retry here. /test e2e-aws-builds |
CI failure |
spoke with @bparees and @gabemontero the single failing build test does not appear to be related to this change and keeping the signal for changes to builds is valuable. We will manually merge this and watch the results today. |
@@ -22,6 +22,7 @@ var _ = g.Describe("[registry][Serial][Suite:openshift/registry/serial] Image si | |||
) | |||
|
|||
g.It("can push a signed image to openshift registry and verify it", func() { | |||
g.Skip("disable because containers/image: https://github.com/containers/image/pull/570") |
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.
Good riddance 👏 🎉. Out of curiously, has this been publicly announced somewhere (ahead of 4.0 changelogs)? |
(Used "Red Hat-Managed" option, which is presently hidden for most external users - it's partially, but not yet fully, what one will get in OpenShift Dedicated 4.1. May differ slightly from self-installed OCP?) env DIR=openshift-4.1.0-rc.3 URL="https://api.cben-oapi.bexf.p1.openshiftapps.com:6443" WAIT_OKS="healthz readyz" tools/scrape.sh --insecure - Notably /oapi is completely gone now! (openshift/origin#21782) - TODO: /version/openshift no longer available (openshift/origin#21434) Probably need to scrape `oc get clusterversion` operator CR?
- Use docker:// instead of atomic:, as recommended back in openshift#21782 (comment) openshift#21782 (comment) - Then re-enable the test Signed-off-by: Miloslav Trmač <mitr@redhat.com>
- Use docker:// instead of atomic:, as recommended back in openshift#21782 (comment) openshift#21782 (comment) - Then re-enable the test Signed-off-by: Miloslav Trmač <mitr@redhat.com>
- Use docker:// instead of atomic:, as recommended back in openshift#21782 (comment) openshift#21782 (comment) - Then re-enable the test Signed-off-by: Miloslav Trmač <mitr@redhat.com>
- Use docker:// instead of atomic:, as recommended back in openshift#21782 (comment) openshift#21782 (comment) - Then re-enable the test Signed-off-by: Miloslav Trmač <mitr@redhat.com>
- Use docker:// instead of atomic:, as recommended back in openshift#21782 (comment) openshift#21782 (comment) Signed-off-by: Miloslav Trmač <mitr@redhat.com>
realistically, I'm not going to get to this for a while.
@soltysh @sttts post-rebase I suppose,