Bug 2012564
| Summary: | MTV 2.1.0 cannot be upgraded to 2.2.0 | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Migration Toolkit for Virtualization | Reporter: | Maayan Hadasi <mguetta> | ||||
| Component: | General | Assignee: | Franco Bladilo <fbladilo> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Maayan Hadasi <mguetta> | ||||
| Severity: | high | Docs Contact: | Avital Pinnick <apinnick> | ||||
| Priority: | high | ||||||
| Version: | 2.2.0 | CC: | apinnick, fbladilo, fdupont, istein | ||||
| Target Milestone: | --- | ||||||
| Target Release: | 2.2.0 | ||||||
| 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: | 2021-12-09 19:20:58 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: | |||||||
| Attachments: |
|
||||||
|
Description
Maayan Hadasi
2021-10-10 10:06:35 UTC
Created attachment 1832826 [details]
MTV 2.2.0-43 CatalogSource
Updating that MTV 2.2.0-43 CatalogSource doesn't provide an option to install MTV 2.1.0 (attached screenshot)
Please verify with mtv-operator-bundle-operator-2.2.0-77 / iib:131905, or later. Upgrade MTV 2.1 to MTV 2.2 fails using MTV 2.2.0-80 / iib: 132252 CatalogSource Though I am able to deploy MTV 2.1 using MTV 2.2 catsrc, there is no available upgrade when changing the 'Update channel' to 2.2 in order to upgrade to 2.2 Steps to Reproduce: 1. Install MTV 2.1 operator using 2.2.0 catalog source CR 2. In OCP UI go to Installed Operators -> MTV -> Subscription 3. Select Update channel: release-v2.2.0 Actual results: There is no available upgrade Moving to ASSIGNED Please verify with mtv-operator-bundle-operator-2.2.0-81 / iib:132643, or later. Bug was moved to ASSIGNED since the upgrade still fails. The root cause is a change on the migration and plan CRDs with a new required field, when an upgrade with existing plans/migration CRs is triggered from 2.1.0 -> 2.2.0 OLM refuses to continue. Mayaan Hadasi performed an upgrade from 2.1.0 -> 2.2.0 without existing CRs. That worked, but required also a restart of the catalog source before running the upgrade to 2.2.0. Is this a bug? This is a bug. What is the new required field? (In reply to Fabien Dupont from comment #6) > This is a bug. What is the new required field? restorePowerState MTV upgrade failed with this error: Danger alert:Failed error validating existing CRs against new CRD's schema for "migrations.forklift.konveyor.io": error validating custom resource against new schema for Migration openshift-mtv/mtv-api-tests-21-10-11-10-36-09-ad3-migration: [].status.vms.restorePowerState: Required value See build 2.2.0-87 Please verify with mtv-operator-bundle-container-2.2.0-87 / iib:134964, or later. MTV was upgraded from 2.1 to 2.2.0-88 build (using 2.2.0-88 CatalogSource), warm and cold migrations ended successfully after the upgrade. - Still have to restart catalog-source pod, we see the same behavior using MTV image from stage Moving to VERIFIED, based on MTV upgrade testing (comment #10) We will open a Doc bug regarding the required restart of the CatalogSource pod if we see it again in stage. Versions: MTV 2.2.0-88 / iib:135478 (was upgraded from MTV 2.1.0 GA) CNV 4.9.1-23 / iib:133012 OCP 4.9.7 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (MTV 2.2.0 Images), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2021:5066 |