-
Notifications
You must be signed in to change notification settings - Fork 545
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
Cannot upgrade operator from v1alpha1 to v1beta1 #1180
Comments
Without further information, my guess is that the update is failing due to your changes to the underlying CRDs. Please see this doc: https://github.com/operator-framework/operator-lifecycle-manager/blob/master/doc/design/dependency-resolution.md#add-a-new-version-to-crd On how CRD updates must be handled to ensure your update doesn’t break existing installations. To further debug, could you show:
|
@ecordell Thanks for your support. Here are further debug information: the status of the subscription
the status of the installplan
the status of any csvs (do you see the new CSV get created at all?) I did not saw any new CSV get created.
the logs of olm-operator and catalog-operator in openshift-operator-lifecycle-manager |
@clyang82 Your subscription specifies If you try with |
Yes. it works after changing subscription with |
I am running an example
app-operator
on top of openshift 4.2. the olm version is 0.11. I have create the app-operator version 0.0.1/0.0.2/1.0.0. I can successfully upgrade from 0.0.1 to 0.0.2 by using olm. After pushed a new version 1.0.0 with the version change to v1beta1, then the operator cannot be upgraded successfully.the catalogsource shows the 1.0.0 is loaded
the packagemanifest shows the v1beta1 information as well
The example source code is in https://github.com/clyang82/app-operator/tree/1.0.0/deploy/olm-catalog/app-operator
Am I missed anything? Which logs I need to check further? Thanks for your help.
The text was updated successfully, but these errors were encountered: