Description of problem: Velero deployment fails on OCP 3.9 and 3.10 using latest CAM 1.2.0 , see : See the following operator ansible container error : fatal: [localhost]: FAILED! => {"changed": false, "error": 422, "msg": "Failed to create object: b'{\"kind\":\"Status\",\"apiVersion\":\"v1\",\"metadata\":{},\"status\":\"Failure\",\"message\":\"CustomResourceDefinition.apiextensions.k8s.io \\\\\"backups.velero.io\\\\\" is invalid: [spec.validation.openAPIV3Schema.properties[spec].properties[hooks].properties[resources].items.properties[labelSelector].properties[matchLabels].additionalProperties: Forbidden: additionalProperties cannot be set to false, spec.validation.openAPIV3Schema.properties[spec].properties[labelSelector].properties[matchLabels].additionalProperties: Forbidden: additionalProperties cannot be set to false]\",\"reason\":\"Invalid\",\"details\":{\"name\":\"backups.velero.io\",\"group\":\"apiextensions.k8s.io\",\"kind\":\"CustomResourceDefinition\",\"causes\":[{\"reason\":\"FieldValueForbidden\",\"message\":\"Forbidden: additionalProperties cannot be set to false\",\"field\":\"spec.validation.openAPIV3Schema.properties[spec].properties[hooks].properties[resources].items.properties[labelSelector].properties[matchLabels].additionalProperties\"},{\"reason\":\"FieldValueForbidden\",\"message\":\"Forbidden: additionalProperties cannot be set to false\",\"field\":\"spec.validation.openAPIV3Schema.properties[spec].properties[labelSelector].properties[matchLabels].additionalProperties\"}]},\"code\":422}\\n'", "reason": "Unprocessable Entity", "status": 422} Version-Release number of selected component (if applicable): v1.2.0 How reproducible: Attempt to deploy CAM on OCP 3.9 or 3.10 Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Successful deployment Additional info: See : https://github.com/konveyor/mig-operator/issues/321
https://github.com/konveyor/mig-operator/pull/328
https://github.com/konveyor/mig-operator/pull/331/files will be the real fix since I inverted the conditional checks.
Verified using CAM 1.2 stage openshift-migration-rhel7-operator@sha256:6afd508558cdbfdfa05b46d0d02c46af59404a1f2bfd09c3272bbcf41900996d $ oc version oc v3.9.0+191fece kubernetes v1.9.1+a0ce1bc657 features: Basic-Auth GSSAPI Kerberos SPNEGO Server https://ec2-54-198-106-202.compute-1.amazonaws.com:8443 openshift v3.9.97 kubernetes v1.9.1+a0ce1bc657 $ oc get pods NAME READY STATUS RESTARTS AGE migration-controller-694cf99845-2tb7l 2/2 Running 0 1h migration-operator-75d7b85555-cz6tc 2/2 Running 0 1h migration-ui-788f486785-9rwx9 1/1 Running 0 1h registry-b3466e42-9508-11ea-9371-0edae747cb01-mnb5r-1-tmwrc 1/1 Running 0 16m restic-hp6td 1/1 Running 0 12m restic-l2k7t 1/1 Running 0 12m restic-nl2nh 1/1 Running 0 12m restic-vmplj 1/1 Running 0 12m velero-59f7946f7f-tfx5b 1/1 Running 0 1h $ oc version oc v3.11.126 kubernetes v1.11.0+d4cacc0 features: Basic-Auth GSSAPI Kerberos SPNEGO Server https://ec2-3-89-153-192.compute-1.amazonaws.com:8443 openshift v3.10.181 kubernetes v1.10.0+b81c8f8 $ oc get pods NAME READY STATUS RESTARTS AGE migration-operator-79b5d4c84c-b5xbh 2/2 Running 0 6m restic-5x48r 1/1 Running 0 4m restic-dfw8b 1/1 Running 0 4m restic-vss89 1/1 Running 0 4m velero-7fdf578bc-dmdgr 1/1 Running 0 4m
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, 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-2020:2326