Bug 1807460
| Summary: | Failed to deploy migration-controller (CAM 1.1.1) through OperatorHub in OCP 4.4 | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | whu |
| Component: | Migration Tooling | Assignee: | Dylan Murray <dymurray> |
| Status: | CLOSED ERRATA | QA Contact: | whu |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 4.3.0 | CC: | dymurray, sregidor, whu, xjiang |
| Target Milestone: | --- | ||
| Target Release: | 4.3.z | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | No Doc Update | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-04-23 17:26: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: | |||
https://github.com/konveyor/mig-operator/pull/232 https://github.com/konveyor/mig-operator/pull/233 https://github.com/konveyor/mig-controller/pull/446 Fix is in: openshift-migration-operator-metadata-container-v1.1-13 openshift-migration-operator-container-v1.1-9 openshift-migration-controller-container-v1.1-6 Stage CAM 1.1.2 can be deployed in OCP 4.4 $ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.4.0-0.nightly-2020-03-20-065504 True False 46m Cluster version is 4.4.0-0.nightly-2020-03-20-065504 $ oc get pods -n openshift-migration NAME READY STATUS RESTARTS AGE catalog-cb2pk 1/1 Running 1 34m migration-controller-dc94f8bbb-gs7lh 2/2 Running 0 16m migration-operator-c5977dc5c-7rvjs 2/2 Running 0 22m migration-ui-d85f59696-f7jp4 1/1 Running 0 16m restic-khjm5 1/1 Running 0 16m restic-nxvh8 1/1 Running 0 16m restic-wsflw 1/1 Running 0 16m velero-fb57f74f-nthm2 1/1 Running 0 16m 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/RHBA-2020:1554 |
Description of problem: When deploy CAM 1.1.1 through OperatorHub in OCP 4.4 cluster, the migration-controller failed to be deployed. How reproducible: Steps to Reproduce: 1 In the OpenShift Container Platform web console, click Administration → Namespaces. 2 On the Namespaces page: 2.1 Click Create Namespace. 2.2 Enter openshift-migration in the Name field and click Create. 3 Click Operators → OperatorHub. 4 On the OperatorHub page: 4.1 Scroll or type a keyword into the Filter by keyword field (in this case, Migration) to find the Cluster Application Migration Operator. 4.2 Select the Cluster Application Migration Operator and click Install. 5 On the Create Operator Subscription page: 5.1 Select the openshift-migration namespace if it is not already selected. 5.2 Select an Automatic or Manual approval strategy. 5.3 Click Subscribe. 6 Click Operators → Installed Operators. 7 On the Installed Operators page: 7.1 Under Provided APIs, click View 12 more…. 7.2 Click Create New → MigrationController. 7.3 Click Create. Actual results: Failed to deploy `MigrationController`. Got below error from ansible container log. --------------------------------- $ oc logs migration-operator-5ccf958f65-hx44q -c ansible ........ TASK [migrationcontroller : Set up velero controller] ************************** task path: /opt/ansible/roles/migrationcontroller/tasks/main.yml:147 fatal: [localhost]: FAILED! => {"changed": false, "msg": "Failed to find exact match for apps/v1beta1.Deployment by [kind, name, singularName, shortNames]"} ........ --------------------------------- Expected results: There is no error when deploy `MigrationController`,