-
Notifications
You must be signed in to change notification settings - Fork 551
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
🌱 update skopeo openshift test #3298
🌱 update skopeo openshift test #3298
Conversation
Signed-off-by: Per Goncalves da Silva <[email protected]>
296eba4
to
61e4abc
Compare
@@ -2601,13 +2601,13 @@ var _ = Describe("Subscription", func() { | |||
sub, err = fetchSubscription(crc, generatedNamespace.GetName(), subName, subscriptionHasCurrentCSV("example-operator.v0.3.0")) | |||
Expect(err).Should(BeNil()) | |||
|
|||
By("waiting for the subscription to have v0.3.0 installed with a Package deprecated condition") | |||
By("waiting for the subscription to have v0.3.0 installed without a bundle deprecated condition") |
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.
What this test really wants to test is that bundle deprecation condition is gone. So, let's just test for that.
If this is the fastest way to handle this, I'm not opposed to the change, but is there a reason we can't shift openshift specific stuff out of this repository entirely? |
61e4abc
to
b606c14
Compare
I have that on my list of things. Let's deal with getting downstream green first though and yanks this out as it's own task. |
Signed-off-by: Per Goncalves da Silva <[email protected]>
b606c14
to
a937352
Compare
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.
/lgtm
37dcff4
Description of the change:
This update does not affect OLM. This updates an e2e test that is used downstream by Red Hat. This PR updates the version of skopeo used in the test as well as the way the skopeo pod is built for it. Now, we mount the secret as a volume and convert its contents to an auth.json file that skopeo can use and also mount an emptydir as a local cache for skopeo (something the logs showed skopeo was complaining about). I've reproduced this issue and tested this fix using an Openshift cluster.
Motivation for the change:
The test expected Openshift to add credential annotations in a secret that contains the auth configuration for the internal registry.
Architectural changes:
Testing remarks:
Reviewer Checklist
/doc
[FLAKE]
are truly flaky and have an issue