Bug 1960410 - Migration with "Verify" enabled in spec fails because the "v1beta1.Daemonset" extensions are not found on the target cluster
Summary: Migration with "Verify" enabled in spec fails because the "v1beta1.Daemonset"...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Migration Toolkit for Containers
Classification: Red Hat
Component: Controller
Version: 1.4.3
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: ---
: 1.5.0
Assignee: John Matthews
QA Contact: Xin jiang
Avital Pinnick
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-05-13 19:33 UTC by Alay Patel
Modified: 2022-01-05 05:00 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-07-28 04:08:07 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github konveyor mig-controller pull 1111 0 None open Bug 1960410: use appsv1 instead of old extensions/v1beta1, rely on compat client 2021-05-19 16:24:23 UTC
Red Hat Product Errata RHEA-2021:2929 0 None None None 2021-07-28 04:08:15 UTC

Description Alay Patel 2021-05-13 19:33:33 UTC 
Description of problem:
The compat client downconverts the APIs but does not upconvert. The mig-controller has hard-coded value of v1beta1.Daemonset, it should be instead appsv1.Daemonset, so we try for the latest and than if needed compact client can down convert. This only happens when verify: true is selected in the migplan.

Because the v1beta1.Daemonset is not available API in some of the recent versions of OCP, the migration fails with an error message

```
"error":"no matches for kind \"DaemonSet\" in versioin \"extensions/v1beta1\""
```


Version-Release number of selected component (if applicable):
1.4.3


How reproducible:
Always when verify is on

Steps to Reproduce:
1. Turn verify to true in the migplan
2. create a migmigration for the migplan from the CLI
3. run the migmigration

Actual results:
Migration should succeed


Expected results:
migration fails with the above message


Additional info:
Comment 8 Xin jiang 2021-07-07 09:14:58 UTC 
verified with  the steps :

1. dd a daemonset on source namespace as the application to migrate
2. create the migplan
3. create the migmigration with spec.verify: true this is not possible using the UI and needs to be done manually
4. wait for the migmgiration to succeed.
Comment 14 errata-xmlrpc 2021-07-28 04:08:07 UTC 
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 (Migration Toolkit for Containers (MTC) image release advisory 1.5.0), 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:2929
Note You need to log in before you can comment on or make changes to this bug.