Description of problem: [MIG UI] Unable to edit namespace selection. Version-Release number of selected component (if applicable): # oc describe pod/migration-ui-6f7df75875-gzjks -n openshift-migration| grep Image Image: image-registry.openshift-image-registry.svc:5000/rhcam/openshift-migration-ui:v1.0 Image ID: image-registry.openshift-image-registry.svc:5000/rhcam/openshift-migration-ui@sha256:59e60d7036ebdc5b7d29895104e7b459a53a1c004e876f50b3e79cdc2b78941c How reproducible: always Steps to Reproduce: 1. On Mig UI select a namespace to migrate 2. click Next 3. Go Back 4. Unselect the above selected namespace and select another one. 5. Click Next. Actual results: The PV's of the very first selected namespace is listed after the second attempt. Expected results: The namespace selection update should update the pv selection Additional info: https://github.com/fusor/mig-ui/pull/590
Provisionally setting target to 4.2. I think there would be a basic expectation that this would work.
I've just tested this and it appears to be fixed as of our current 1.1 release candidate. https://github.com/fusor/mig-ui/pull/655 is certainly related. It wasn't implemented to directly fix this bz, but it potentially has resolved the underlying cause.
Verified in CAM 1.1 stage Controller: image: registry.stage.redhat.io/rhcam-1-1/openshift-migration-controller-rhel8@sha256:ec015e65da93e800a25e522473793c277cd0d86436ab4637d73e2673a5f0083d UI: image: registry.stage.redhat.io/rhcam-1-1/openshift-migration-ui-rhel8@sha256:ecd81e11af0a17bfdd4e6afce1bf60f422115ed3545ad2b0d055f0fded87e422 Migration plan's namespaces can be added/removed/edited now.
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