-
Notifications
You must be signed in to change notification settings - Fork 53
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
entity for package "project-quay" not found in solution
when trying to upgrade to the next version using replaces
#321
Comments
Just noticed that the E2E doesn't not specify a channel. I tested the steps described above, but removed the channel from |
I'm not seeing this problem in v0.3.0, I don't think. |
@joelanford v0.3.0 was cut before #275. So I think we missed something in #275, but I can't figure out what is the difference between my example and the E2E test which works. I'll come back to it on Monday. |
From @jmprusi:
We might need to add toleration for versions with Another option is to not allow v prefix, but in this case we want need to decide what to do with existing operators. |
I didn't see any |
This turned out to be unrelated to operator-controller/testdata/catalogs/test-catalog/catalog.yaml Lines 6 to 14 in dea70eb
It looks like replaces in the test are in format Most likely this means that controller also builds the problem incorrectly (using package name). |
I'm getting
entity for package "project-quay" not found in solution
when trying to upgrade to the next version.project-quay
usesreplaces
to speficy upgrade edges and support for this was added #275. I see that PR has an e2e test confirming an upgrade so it might be that I'm missing something.Steps to reproduce
kubectl wait operators operator-sample --for condition=Installed
kubectl patch operator operator-sample --type json -p '[{"op": "replace", "path": "/spec/version", "value": "3.8.2"}]'
Output:
Expected results
Operator is correctly resolved and installed
The text was updated successfully, but these errors were encountered: