Bug 1960410

Summary:	Migration with "Verify" enabled in spec fails because the "v1beta1.Daemonset" extensions are not found on the target cluster
Product:	Migration Toolkit for Containers	Reporter:	Alay Patel <alpatel>
Component:	Controller	Assignee:	John Matthews <jmatthew>
Status:	CLOSED ERRATA	QA Contact:	Xin jiang <xjiang>
Severity:	low	Docs Contact:	Avital Pinnick <apinnick>
Priority:	medium
Version:	1.4.3	CC:	ernelson, jmatthew, rhaigner, rjohnson, ssingla
Target Milestone:	---
Target Release:	1.5.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-07-28 04:08:07 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:

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