Bug 2078543
| Summary: | Upgrading from ACM 2.4 to ACM 2.5 failed since InstallPlan was not generated by Subscription | ||
|---|---|---|---|
| Product: | Red Hat Advanced Cluster Management for Kubernetes | Reporter: | Noam Manos <nmanos> |
| Component: | Installer | Assignee: | Jakob <jagray> |
| Status: | CLOSED WORKSFORME | QA Contact: | txue |
| Severity: | low | Docs Contact: | Christopher Dawson <cdawson> |
| Priority: | unspecified | ||
| Version: | rhacm-2.5 | CC: | ecai, njean |
| Target Milestone: | --- | Flags: | bot-tracker-sync:
rhacm-2.5+
|
| Target Release: | rhacm-2.5.1 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-10-06 12:52:16 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 2058417 | ||
| Bug Blocks: | |||
|
Description
Noam Manos
2022-04-25 14:50:06 UTC
G2Bsync 1108934073 comment JakobGray Mon, 25 Apr 2022 19:06:19 UTC G2Bsync Since this is a recognized issue with Openshift I don't think there is anything we can do to fix it and will need to wait for a patch from the Openshift team When upgrading an operator you should not create a new subscription. If you wish to update for 2.4 to 2.5 you should update the existing subscription's channel from release-2.4 to release-2.5. In manual mode you may also need to remove the starting csv field and approve an install plan. Hi @nmanos , in reading Jakob's comment above, is this a valid test? If it is valid, would it still be a High severity (Sev-1)? When you tried the upgrade by updating existing subscription channel were you using one catalogsource or two different sources like in your original post? ``` NAME PACKAGE SOURCE CHANNEL advanced-cluster-management-release-2.4-subscription advanced-cluster-management advanced-cluster-management-release-2-4-catalog release-2.4 advanced-cluster-management-release-2.5-subscription advanced-cluster-management advanced-cluster-management-release-2-5-catalog release-2.5 ``` I learned from some QE people that some of the upgrade tooling being used by QE was not using the same catalogsource, but that has since been corrected. I've also heard that people have encountered issues before when upgrading while not at the latest z-stream version of a channel. When you are upgrading from 2.4.2 is that the latest version available in the 2.4 channel? If not you should update to whatever is current before upgrading to 2.5. I am not yet able to replicate this issue using 2.5.0-DOWNSTREAM-2022-05-13-16-47-16 from acm-d/acm-custom-registry. At the begging I tried to delete existing subscription and catalog source (of ACM 2.4), and then create a new subscription and catalog source - with the same names as before, but for ACM 2.5. This did not work. On another test scenario (from scratch) I tried to keep the existing subscription + catalog source (of ACM 2.4), and create a new subscription + catalog source for ACM 2.5. This did not work either. Since it's a manual install plan, it will not auto-update to latest minor version (e.g 2.4.2 --> 2.4.3), as far as I understand. In addition, I did not see any instructions/requirements for the user to do a minor upgrade, before attempting a major upgrade (to 2.5) The dependency on bug 2058417 (Subscription has olm.generated-by annotation but missing InstallPlanRef and installplan) is still relevant. To workaround this issue - Delete previous Subscription and CSV from the ACM namespace ("ocm"): $ oc delete subs --all -n ocm --wait subscription.operators.coreos.com "old-operator-subscription" deleted $ oc delete csv --all -n ocm --wait clusterserviceversion.operators.coreos.com "old-operator.v2.4.2" deleted Once the previous CSV and Subscription (of ACM 2.4.2) were deleted, the new Subscription (of ACM 2.5.0) initiates a new InstallPlan, that upgrades the Operator bundle from ACM 2.4.2 to ACM 2.5.0. I have not encountered others with this issue, nor have I been able to replicate it myself. The bug you reference has since been closed. I'd like to close this as well if it's not still happening. |