Description of problem: The CAM operator fails to install its components in a cluster that has two API groups that provide a Route kind. This is because the discovery route only specifies `v1` as its API, instead of the fully qualified `route.openshift.io/v1`. An example of how this would happen is if the user has KNative installed in their cluster. Version-Release number of selected component (if applicable): 1.1.2 How reproducible: Every time Steps to Reproduce: 1. Install KNative 2. Install CAM operator and create a MigrationController CR Actual results: CAM fails to install its components, erroring on the discovery Route creation Expected results: Discovery Route should create with the rest of the CAM components successfully.
https://github.com/konveyor/mig-operator/pull/342
Verified using CAM 1.2 stage. CAM can be installed without problems in a cluster with knative installed. $ oc get pods -n openshift-operators NAME READY STATUS RESTARTS AGE knative-eventing-operator-7877888b66-g2zjs 1/1 Running 0 25m knative-openshift-689c5c58d7-8dj6c 1/1 Running 0 25m knative-openshift-ingress-d8bd76d4f-dw76g 1/1 Running 0 25m knative-serving-operator-65b64c98f8-t5ltq 1/1 Running 0 25m $ oc get pods NAME READY STATUS RESTARTS AGE migration-controller-6579f7854d-29t2b 2/2 Running 0 6m33s migration-operator-d7fc9ffb9-djgxr 2/2 Running 0 7m41s migration-ui-dbf4bb46f-c8jzj 1/1 Running 0 6m27s restic-5r8dz 1/1 Running 0 6m54s restic-ch27n 1/1 Running 0 6m54s restic-gvc9v 1/1 Running 0 6m54s restic-kkfr6 1/1 Running 0 6m54s velero-7d94b87d6f-hkhv4 1/1 Running 0 6m54s
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