-
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
Make admission extended tests dockerless #21416
Conversation
/test extended_image_registry |
test/extended/images/helper.go
Outdated
return "", err | ||
} | ||
|
||
registryHost, err := GetDockerRegistryURL(oc) |
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 don't think this is going to work. The extended tests don't run within the cluster network anymore, so when you want to interact with a cluster service you need to run your logic within a pod on the cluster.
So either you need to create a route for the registry and then talk to it over that, or (harder) find a way to move this logic into a pod context.
other than the cluster-network access problem, the general concept looks good... |
@dmage you want |
Well, in fact, it makes the main idea of this PR (replace Docker push with the Go client) not viable. Apparently we'll need to rewrite each test from scratch, considering new restrictions. |
/test all |
/retest |
can you make use of |
nm, that would have the same issue of not being able to reach the registry service. |
b10baa6
to
c3f3f14
Compare
@bparees I've updated only tests for quota admission and limit range admission. The tests are green. I'm not sure what to do with pruning tests, |
waitTimeout = time.Second * 600 | ||
) | ||
|
||
var _ = g.Describe("[Feature:ImageQuota][registry][Serial][Suite:openshift/registry/serial][local] Image resource quota", func() { | ||
var _ = g.Describe("[Feature:ImageQuota] Image resource quota", func() { |
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 think this means the test will get run in conformance, but did you confirm you saw it run in one of the job outputs?
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'm not seeing it listed in either e2e-gcp or e2e-gcp-image-registry.
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.
Feature:ImageQuota is disabled in
origin/test/extended/util/test.go
Line 285 in 027d88e
`\[Feature:ImageQuota\]`, // Quota isn't turned on by default, we should do that and then reenable these tests |
And this test no longer depends on the registry, so I removed the [registry] tag.
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 see... well assuming this test works (because image quota is on by default now?) let's re-enable it. If it still can't be run, i guess this is fine.
I see we have another test in the same boat (limitrange_admission).
yes (you can pick an image that already has the oc tool in it, but yes). The typical pattern there is to launch a pod w/ an cmd of "sleep 60000" and then exec into it.
yes, do it as a follow up, let's merge what you've got already. |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bparees, dmage 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 |
/retest Please review the full test history for this PR and help us cut down flakes. |
6 similar comments
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
@dmage: 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. 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. I understand the commands that are listed here. |
/retest Please review the full test history for this PR and help us cut down flakes. |
Fixes 2 of 4 tests described at #20079.