Bug 1777869
| Summary: | [MIG-UI] Wrong storageclass name shown when creating a migration plan | |||
|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Sergio <sregidor> | |
| Component: | Migration Tooling | Assignee: | Erik Nelson <ernelson> | |
| Status: | CLOSED ERRATA | QA Contact: | Sergio <sregidor> | |
| Severity: | medium | Docs Contact: | ||
| Priority: | medium | |||
| Version: | 4.2.0 | CC: | chezhang, ernelson, jmatthew, rpattath, xjiang | |
| Target Milestone: | --- | |||
| Target Release: | 4.3.0 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | No Doc Update | ||
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1778896 (view as bug list) | Environment: | ||
| Last Closed: | 2020-02-06 20:20:49 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: | ||||
| Bug Depends On: | 1778896 | |||
| Bug Blocks: | ||||
The fix was not included in 1.0.1 version. Moved to "assigned" status.
Verified in CAM 1.1 stage
Controller:
image: registry.stage.redhat.io/rhcam-1-1/openshift-migration-controller-rhel8@sha256:ec015e65da93e800a25e522473793c277cd0d86436ab4637d73e2673a5f0083d
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 The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days |
Description of problem: In the volumes screen (step 3) the name of the storage class has a wrong value. Version-Release number of selected component (if applicable): UI image: Release 1.0.1 stored in rh-osbs image: image-registry.openshift-image-registry.svc:5000/rhcam-1-0/openshift-migration-ui-rhel8@sha256:5e04d383b3796982aaf366c7bb6742661bc4b4964a326ee8db20c533f1831342 TARGET CLUSTER: NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.2.0 True False 26h Cluster version is 4.2.0 SOURCE CLUSTER: $ oc version Client Version: version.Info{Major:"4", Minor:"1+", GitVersion:"v4.1.4", GitCommit:"c9e4f28ff", GitTreeState:"clean", BuildDate:"2019-06-26T23:04:27Z", GoVersion:"go1.12.6", Compiler:"gc", Platform:"linux/amd64"} Server Version: version.Info{Major:"1", Minor:"11+", GitVersion:"v1.11.0+d4cacc0", GitCommit:"d4cacc0", GitTreeState:"clean", BuildDate:"2019-11-26T00:42:21Z", GoVersion:"go1.10.8", Compiler:"gc", Platform:"linux/amd64"} How reproducible: Always Steps to Reproduce: Use a source cluster with glusterfs, and a target cluster with ceph. 1. Create a migration plan to migrate a volume that uses "glusterfs-storage" storage class 2. In step 3, verify the storage class name shown Actual results: The storage class shown in step 3 is a ceph storage class, instead of the "glusterfs-storage" storage class actually used in the source cluster. Expected results: Step 3 should show the current storage class used in the source cluster, and not the destination storage class in the target. Additional info: