Bug 1777869 - [MIG-UI] Wrong storageclass name shown when creating a migration plan
Summary: [MIG-UI] Wrong storageclass name shown when creating a migration plan
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Migration Tooling
Version: 4.2.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.3.0
Assignee: Erik Nelson
QA Contact: Sergio
URL:
Whiteboard:
Depends On: 1778896
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-11-28 14:22 UTC by Sergio
Modified: 2023-09-14 05:47 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
: 1778896 (view as bug list)
Environment:
Last Closed: 2020-02-06 20:20:49 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2020:0440 0 None None None 2020-02-06 20:21:06 UTC

Description Sergio 2019-11-28 14:22:29 UTC
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:

Comment 1 Erik Nelson 2019-12-10 19:08:45 UTC
https://github.com/fusor/mig-ui/pull/637

Comment 4 Sergio 2019-12-18 12:39:49 UTC
The fix was not included in 1.0.1 version. Moved to "assigned" status.

Comment 9 Sergio 2020-01-22 09:17:44 UTC
Verified in CAM 1.1 stage
Controller:
    image: registry.stage.redhat.io/rhcam-1-1/openshift-migration-controller-rhel8@sha256:ec015e65da93e800a25e522473793c277cd0d86436ab4637d73e2673a5f0083d

Comment 11 errata-xmlrpc 2020-02-06 20:20:49 UTC
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

Comment 12 Red Hat Bugzilla 2023-09-14 05:47:46 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days


Note You need to log in before you can comment on or make changes to this bug.