+++ This bug was initially created as a clone of Bug #1783363 +++ Description of problem: When "move" action is selected for a glusterfs pvc migration, if there is no OCS4 installed in the target cluster, a PvWarnNoCephAvailable warning is displayed. Version-Release number of selected component (if applicable): TARGET $ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.2.0 True False 25h Error while reconciling 4.2.0: the cluster operator marketplace has not yet successfully rolled out SOURCE $ oc version oc v3.11.126 kubernetes v1.11.0+d4cacc0 features: Basic-Auth GSSAPI Kerberos SPNEGO Server https:// openshift v3.9.99 kubernetes v1.9.1+a0ce1bc657 Controller: Version 1.0.1 osbs registry: image: image-registry.openshift-image-registry.svc:5000/rhcam-1-0/openshift-migration-controller-rhel8@sha256:e2c3cbb61157605d8246496f77c76b9b2950eb951bd0a63d4f8e3ae6f1884c2c How reproducible: Always Steps to Reproduce: To reproduce it, we don't actually need to migrate or prepare a cluster for "move" action. We only need to create the migration plan. 1. Install App Migration with target cluster without OCS4 (ceph), and source cluster with OCS3 (gluster) 2. Create a MigPlan of an application using glusterfs volume from source to target, select "move" action. Actual results: After the MigPlan creation, a warning is shown, saying that it's recommended to use OCS4 storage classes, and that it will be used the default storage class instead. Expected results: Destination storage classes don't make much sense talking about "move" action. No warning should be displayed if the selected action is "move" and not "copy". Additional info:
Fix is here: https://github.com/fusor/mig-controller/pull/387
Verified in CAM 1.1 stage image: registry.stage.redhat.io/rhcam-1-1/openshift-migration-controller-rhel8@sha256:b55c0c36333656a46e1d0500cf11cc8aa06e093d312e7c54f8e1075d4ab4c6c1 Move glusterfs will not result in a warning anymore when ceph is not installed in target cluster. Nevertheless, because of this bug https://bugzilla.redhat.com/show_bug.cgi?id=1791012 the user will still see a warning because of a sync problem between UI and controller.
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:0440