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 "ClusterServiceVersion when a CustomResourceDefinition was installed alongside a ClusterServiceVersion" test failures #2540

Closed
akihikokuroda opened this issue Dec 24, 2021 · 0 comments · Fixed by #2541
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@akihikokuroda
Copy link
Member

akihikokuroda commented Dec 24, 2021

Bug Report

e2e "ClusterServiceVersion when a CustomResourceDefinition was installed alongside a ClusterServiceVersion" failure

https://github.com/operator-framework/operator-lifecycle-manager/runs/4622357457?check_suite_focus=true#step:4:9553

[Fail] ClusterServiceVersion when a CustomResourceDefinition was installed alongside a ClusterServiceVersion [AfterEach] can satisfy an associated ClusterServiceVersion's ownership requirement
/home/runner/work/operator-lifecycle-manager/operator-lifecycle-manager/test/e2e/csv_e2e_test.go:129

[Fail] ClusterServiceVersion when a CustomResourceDefinition was installed alongside a ClusterServiceVersion [BeforeEach] when an unassociated ClusterServiceVersion in different namespace owns the same CRD can satisfy the unassociated ClusterServiceVersion's ownership requirement
/home/runner/work/operator-lifecycle-manager/operator-lifecycle-manager/test/e2e/csv_e2e_test.go:123

What did you do?
e2e test in the CI build failed.

What did you expect to see?
No failure

What did you see instead? Under which circumstances?
Failure above.

The first error is a timeout removing the namespace during the test clean up. The second error is caused by the uncleaned resources by the first error.

Environment

  • operator-lifecycle-manager version:
  • Kubernetes version information:
  • Kubernetes cluster kind:

Possible Solution

Additional context
Add any other context about the problem here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant