Skip to content
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

e2e flake: [FAILED] Operator Install when An operator is installed from an operator catalog #215

Closed
joelanford opened this issue May 16, 2023 · 2 comments · Fixed by #250
Assignees

Comments

@joelanford
Copy link
Member

See: https://github.com/operator-framework/operator-controller/actions/runs/4990417752/jobs/8938348906#step:4:522

• [FAILED] [181.699 seconds]
Operator Install when An operator is installed from an operator catalog [It] resolves the specified package with correct bundle path
/home/runner/work/operator-controller/operator-controller/test/e2e/install_test.go:64

  Timeline >>
  STEP: creating the Operator resource @ 05/16/23 12:15:10.141
  STEP: eventually reporting a successful resolution and bundle path @ 05/16/23 12:15:10.145
  [FAILED] in [It] - /home/runner/work/operator-controller/operator-controller/test/e2e/install_test.go:75 @ 05/16/23 12:15:40.147
  << Timeline

  [FAILED] Timed out after 30.001s.
  The function passed to Eventually failed at /home/runner/work/operator-controller/operator-controller/test/e2e/install_test.go:74 with:
  Expected
      <string>: package 'argocd-operator' not found
  to equal
      <string>: install was successful
  In [It] at: /home/runner/work/operator-controller/operator-controller/test/e2e/install_test.go:75 @ 05/16/23 12:15:40.147
------------------------------

Summarizing 1 Failure:
  [FAIL] Operator Install when An operator is installed from an operator catalog [It] resolves the specified package with correct bundle path
  /home/runner/work/operator-controller/operator-controller/test/e2e/install_test.go:75
@tmshort
Copy link
Contributor

tmshort commented May 23, 2023

From @joelanford.

Issues:

  • The image is pulled from a public image registry over the internet (is quay up? are we being rate-limited?)
  • The image is big (is it taking too long to download/unpack?)
  • The image is always changing and we don’t control the content of it (did the thing we depend on change?)

Things to look at:

  1. Put the image contents + image build in the repo (and then use kind load to get it into the e2e cluster)
  2. Keep the image contents small
  3. Keep the image contents focused on what we’re actually testing

@joelanford
Copy link
Member Author

Put the image contents + image build in the repo (and then use kind load to get it into the e2e cluster)

Doing this part requires a catalogd release that includes operator-framework/catalogd#65

anik120 added a commit to anik120/operator-controller that referenced this issue Jun 2, 2023
This PR
* Stands up a local image registry in the cluster
* Builds bundles and catalog images and uploads them to the image registry
* Uses the custom images in the e2e test suite

* Also introduces a `pullSecret` field for the Operator API's Spec struct,
to allow installation of operators on cluster whose bundles require
imagePullSecret to be provisioned. This is required because the bundle
images built and uploaded to the local registry above requires a pull
secret for the local registry.

closes operator-framework#215
anik120 added a commit to anik120/operator-controller that referenced this issue Jun 2, 2023
This PR
* Stands up a local image registry in the cluster
* Builds bundles and catalog images and uploads them to the image registry
* Uses the custom images in the e2e test suite

* Also introduces a `pullSecret` field for the Operator API's Spec struct,
to allow installation of operators on cluster whose bundles require
imagePullSecret to be provisioned. This is required because the bundle
images built and uploaded to the local registry above requires a pull
secret for the local registry.

closes operator-framework#215
anik120 added a commit to anik120/operator-controller that referenced this issue Jun 2, 2023
closes operator-framework#215

Signed-off-by: Anik <anikbhattacharya93@gmail.com>
anik120 added a commit to anik120/operator-controller that referenced this issue Jun 2, 2023
closes operator-framework#215

Signed-off-by: Anik <anikbhattacharya93@gmail.com>
anik120 added a commit to anik120/operator-controller that referenced this issue Jun 2, 2023
closes operator-framework#215

Signed-off-by: Anik <anikbhattacharya93@gmail.com>
@anik120 anik120 assigned anik120 and unassigned jmprusi and tmshort Jun 2, 2023
anik120 added a commit to anik120/operator-controller that referenced this issue Jun 2, 2023
closes operator-framework#215

Signed-off-by: Anik <anikbhattacharya93@gmail.com>
anik120 added a commit to anik120/operator-controller that referenced this issue Jun 2, 2023
closes operator-framework#215

Signed-off-by: Anik <anikbhattacharya93@gmail.com>
anik120 added a commit to anik120/operator-controller that referenced this issue Jun 2, 2023
closes operator-framework#215

Signed-off-by: Anik <anikbhattacharya93@gmail.com>
anik120 added a commit to anik120/operator-controller that referenced this issue Jun 2, 2023
closes operator-framework#215

Signed-off-by: Anik <anikbhattacharya93@gmail.com>
anik120 added a commit to anik120/operator-controller that referenced this issue Jun 2, 2023
closes operator-framework#215

Signed-off-by: Anik <anikbhattacharya93@gmail.com>
anik120 added a commit to anik120/operator-controller that referenced this issue Jun 5, 2023
closes operator-framework#215

Signed-off-by: Anik <anikbhattacharya93@gmail.com>
everettraven pushed a commit to everettraven/operator-controller that referenced this issue Jun 6, 2023
closes operator-framework#215

Signed-off-by: Anik <anikbhattacharya93@gmail.com>
everettraven pushed a commit to everettraven/operator-controller that referenced this issue Jun 6, 2023
closes operator-framework#215

Signed-off-by: Anik <anikbhattacharya93@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

4 participants