Bug 1981537 - MTC cannot be deployed on OpenShift Container Platform version 3.10
Summary: MTC cannot be deployed on OpenShift Container Platform version 3.10
Alias: None
Product: Migration Toolkit for Containers
Classification: Red Hat
Component: Operator
Version: 1.4.5
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 1.4.6
Assignee: John Matthews
QA Contact: Xin jiang
Avital Pinnick
Depends On: 1981335 1981717 1983669
TreeView+ depends on / blocked
Reported: 2021-07-12 18:39 UTC by Erik Nelson
Modified: 2021-07-21 17:05 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1981335
Last Closed: 2021-07-21 17:05:27 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github konveyor mig-operator pull 714 0 None open Bug 1981537: Remove additionalProperties validation from DVMP CRD (#711) 2021-07-13 14:21:47 UTC
Red Hat Product Errata RHBA-2021:2854 0 None None None 2021-07-21 17:05:29 UTC

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:

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
Forbidden\\\",\\\"message\\\":\\\"Forbidden: additionalProperties cannot be set to false\\\",\\\"field\\\":\\\"spec.validation.openAPIV3Schema.properties[spec]

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.


Note You need to log in before you can comment on or make changes to this bug.