Bug 1898542
| Summary: | [MTC-UI] Target storage classes not detected in the UI | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Migration Toolkit for Containers | Reporter: | Sergio <sregidor> | ||||
| Component: | General | Assignee: | Erik Nelson <ernelson> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Xin jiang <xjiang> | ||||
| Severity: | medium | Docs Contact: | Avital Pinnick <apinnick> | ||||
| Priority: | unspecified | ||||||
| Version: | 1.3.z | CC: | chezhang, ernelson, rjohnson, rpattath, whu, xjiang | ||||
| Target Milestone: | --- | ||||||
| Target Release: | 1.3.z | ||||||
| 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: | 2020-11-30 06:53:04 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: | |||||||
| Attachments: |
|
||||||
*** Bug 1893023 has been marked as a duplicate of this bug. *** Verified using CAM 1.3.2 stage openshift-migration-rhel7-operator@sha256:9b90ee8ad3c39df9f698164accc93720da9009db6a5f54be7aece258e353d578 Target cluster's storage classes are displayed properly. Moved to VERIFIED status. UI image used to verify the bug
- name: MIG_UI_REPO
value: openshift-migration-ui-rhel8@sha256
- name: MIG_UI_TAG
value: a616ba1d16459b376e2a8c77ecc8c0d2122fd04881cf3493d422184434ddd559
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 (Migration Toolkit for Containers (MTC) tool image release advisory 1.3.2), 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:5133 |
Created attachment 1730143 [details] Screenshot Description of problem: The UI cannot detect the right storage classes in the target cluster. Version-Release number of selected component (if applicable): MTC 1.3.2 TARGET CLUSTER: OCP 4.6 AWS SOURCE CLUSTER: OCP 3.11 AWS How reproducible: Always Steps to Reproduce: 1. Deploy an application with one PVC in the source cluster oc new-project bztest oc new-app django-psql-persistent 2. Use the UI to create a migration plan for this application Actual results: In the screen where the target storage class should be selected, we click on the "Targe storage class" item to select the right one and the only option shown is "None". Expected results: All storages classes in the target cluster should be displayed when we try to choose the target storage class. Additional info: In target cluster we have these SCs $ oc get sc NAME PROVISIONER RECLAIMPOLICY VOLUMEBINDINGMODE ALLOWVOLUMEEXPANSION AGE gp2 (default) kubernetes.io/aws-ebs Delete WaitForFirstConsumer true 68m gp2-csi ebs.csi.aws.com Delete WaitForFirstConsumer true 68m In source cluster we have these SCs $ oc get sc NAME PROVISIONER AGE gp2 (default) kubernetes.io/aws-ebs 3h The migcluster has the right storageclasses in it: spec: isHostCluster: true storageClasses: - accessModes: - ReadWriteOnce default: true name: gp2 provisioner: kubernetes.io/aws-ebs - accessModes: - ReadWriteOnce name: gp2-csi provisioner: ebs.csi.aws.com