Bug 1741858
| Summary: | Migration controller creation using OLM does not work with velero 1.1 | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Roshni <rpattath> |
| Component: | Migration Tooling | Assignee: | Derek Whatley <dwhatley> |
| Status: | CLOSED ERRATA | QA Contact: | Xin jiang <xjiang> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 4.2.0 | CC: | chezhang, jmontleo, jortel, sregidor, sseago |
| Target Milestone: | --- | ||
| Target Release: | 4.2.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-10-16 06:36:19 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: | |||
|
Description
Roshni
2019-08-16 09:35:13 UTC
Roshni, thanks for your bug hunting. I'm removing 'testblocker' since we have workaround (other methods to install controller+UI). Hey @Scott, Are you able to provide any insight into what changed with Velero 1.1 that is causing this, and any workaround effort that might be in-progress? Think I recall you mentioning this issue. Also, Roshni, this is probably something that changed since this bug was reported but we are now deploying everything into the `openshift-migration` namespace instead of `mig`. Roshni and Zihan, This issue should have been resolved by https://github.com/fusor/mig-operator/pull/41. Please clean your cluster following directions from https://github.com/fusor/mig-operator#cleanup, delete and re-create https://github.com/fusor/mig-operator/blob/master/mig-operator-source.yaml, and then deploy mig-operator into the "openshift-migration" namespace with OperatorHub + OLM. Deploying with the defaults present in the Web UI should lead to a successful deploy. apiVersion: migration.openshift.io/v1alpha1 kind: MigrationController metadata: creationTimestamp: 2019-08-27T19:43:25Z generation: 1 name: migration-controller namespace: openshift-migration resourceVersion: "4939208" selfLink: /apis/migration.openshift.io/v1alpha1/namespaces/openshift-migration/migrationcontrollers/migration-controller uid: ef6779ab-c902-11e9-8c91-0a0c514fad3a spec: cluster_name: host migration_controller: true migration_ui: true migration_velero: true olm_managed: true $ oc get pods NAME READY STATUS RESTARTS AGE controller-manager-7c9565c55d-n4kch 1/1 Running 0 16m migration-operator-699945c4b5-72fsh 2/2 Running 0 17m migration-ui-6bbf5fc8cd-rnw9k 1/1 Running 0 15m restic-dv8cc 1/1 Running 0 16m restic-sf5zr 1/1 Running 0 16m velero-57fc85c447-gbpsp 1/1 Running 0 16m Verified on OCP 4.2 cluster and it works now. $oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.2.0-0.nightly-2019-08-27-222856 True False 82m Cluster version is 4.2.0-0.nightly-2019-08-27-222856 $oc get pod -n openshift-migration ✔ 2579 13:06:41 NAME READY STATUS RESTARTS AGE controller-manager-7485dfd885-985m9 1/1 Running 0 2m21s migration-operator-987b669d4-sdzgw 2/2 Running 0 2m51s migration-ui-99578967c-6bv9k 1/1 Running 0 2m12s restic-f8dbw 1/1 Running 0 2m22s restic-zjb98 1/1 Running 0 2m22s velero-77f99b46b4-26zr6 1/1 Running 0 2m22s 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-2019:2922 |