Bug 1981537

Summary:	MTC cannot be deployed on OpenShift Container Platform version 3.10
Product:	Migration Toolkit for Containers	Reporter:	Erik Nelson <ernelson>
Component:	Operator	Assignee:	John Matthews <jmatthew>
Status:	CLOSED ERRATA	QA Contact:	Xin jiang <xjiang>
Severity:	urgent	Docs Contact:	Avital Pinnick <apinnick>
Priority:	urgent
Version:	1.4.5	CC:	apinnick, ernelson, jmatthew, rjohnson, sregidor, xjiang
Target Milestone:	---
Target Release:	1.4.6
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1981335	Environment:
Last Closed:	2021-07-21 17:05:27 UTC	Type:	---
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:	1981335, 1981717, 1983669
Bug Blocks:

Description Erik Nelson 2021-07-12 18:39:05 UTC

+++ This bug was initially created as a clone of Bug #1981335 +++

Description of problem:
When we try to deploy MTC in a 3.10 cluster the operator reports an error and fail. The logs pod are not created.

Version-Release number of selected component (if applicable):
MTC 1.5.0
AWS 3.10

How reproducible:
Always

Steps to Reproduce:
1. Deploy MTC in a 3.10 cluster

Actual results:
We get this error in the operator pod

^Mfailed: [localhost] (item=migration.openshift.io_directvolumemigrationprogresses.yaml) => {\"ansible_loop_var\": \"item\", \"changed\": false, \"error\": 422
, \"item\": \"migration.openshift.io_directvolumemigrationprogresses.yaml\", \"msg\": \"Failed to create object: b'{\\\"kind\\\":\\\"Status\\\",\\\"apiVersion\
\\":\\\"v1\\\",\\\"metadata\\\":{},\\\"status\\\":\\\"Failure\\\",\\\"message\\\":\\\"CustomResourceDefinition.apiextensions.k8s.io \\\\\\\\\\\"directvolumemig
rationprogresses.migration.openshift.io\\\\\\\\\\\" is invalid: spec.validation.openAPIV3Schema.properties[spec].properties[podSelector].additionalProperties: 
Forbidden: additionalProperties cannot be set to false\\\",\\\"reason\\\":\\\"Invalid\\\",\\\"details\\\":{\\\"name\\\":\\\"directvolumemigrationprogresses.mig
ration.openshift.io\\\",\\\"group\\\":\\\"apiextensions.k8s.io\\\",\\\"kind\\\":\\\"CustomResourceDefinition\\\",\\\"causes\\\":[{\\\"reason\\\":\\\"FieldValue
Forbidden\\\",\\\"message\\\":\\\"Forbidden: additionalProperties cannot be set to false\\\",\\\"field\\\":\\\"spec.validation.openAPIV3Schema.properties[spec]
.properties[podSelector].additionalProperties\\\"}]},\\\"code\\\":422}\\\

And the MTC logs pod are not created. We are not sure if that impacts more resources apart from the logs pods, probably yes.

Expected results:
The deployment should be executed without errors and all MTC pods should be created successfuly and the operator should report no errors.

Additional info:

Attached must-gather.gz

Comment 5 Sergio 2021-07-19 12:34:07 UTC

Verified using MTC 1.4.6

Verified using the automatic jenkins installation. Jenkins is now down because of PSI issues, as soon as it is up again I will double check. But jenkins automatic verification should be enough.

Comment 9 errata-xmlrpc 2021-07-21 17:05:27 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) 1.4.6 release advisory), 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/RHBA-2021:2854