Bug 1746899 - MIG UI: Clicking the migration plan delete buton does not delete the plan.
Summary: MIG UI: Clicking the migration plan delete buton does not delete the 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
high
Target Milestone: ---
: 4.2.0
Assignee: Erik Nelson
QA Contact: Roshni
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-08-29 13:15 UTC by Roshni
Modified: 2019-10-16 06:38 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-16 06:38:33 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:2922 0 None None None 2019-10-16 06:38:41 UTC

Description Roshni 2019-08-29 13:15:31 UTC
Description of problem:
MIG UI: Clicking the migration plan delete buton does not delete the plan.

Version-Release number of selected component (if applicable):
Image:          quay.io/ocpmigrate/mig-ui:stable
    Image ID:       quay.io/ocpmigrate/mig-ui@sha256:f38a52d944227cb7b9e7e175a2dc0df0ae032fd67cdffd8f11a9c4d73855153d

Image:         quay.io/ocpmigrate/mig-operator:stable
    Image ID:      quay.io/ocpmigrate/mig-operator@sha256:e9f7132c9f87c243574274720eb8938896b949e5ab276bdd267ca249f7b2e604

 Image:         quay.io/ocpmigrate/mig-controller:stable
    Image ID:      quay.io/ocpmigrate/mig-controller@sha256:7ec48a557240f1d2fa6ee6cd62234b0e75f178eca2a0cc5b95124e01bcd2c114

4.2 - 4.2.0-0.nightly-2019-08-28-083236


How reproducible:
always

Steps to Reproduce:
1. install mig-controller & mig-ui on OCP4, and add ocp 3 & s3 bucket to the controller in UI.
2. create a project test to migrate
3. create a migplan using UI to migration project test.
4. do migration from UI, this will succeed.
5. delete migplan from UI, 


Actual results:
The plan is not deleted.

Expected results:
The plan should be deleted

Additional info:
Seeing error message in the controller pod - https://bugzilla.redhat.com/show_bug.cgi?id=1738840#c4

Comment 1 Erik Nelson 2019-09-10 21:38:29 UTC
Enough has changed here that I think it's probably fixed. Going to move to ON_QA; please evaluate if this is still an issue.

Comment 2 Erik Nelson 2019-09-10 22:31:41 UTC
We have some new images we're targeting for release, release-1.0. Checkout the release operator from this branch: https://github.com/fusor/mig-operator/tree/release-1.0, and then install the operator.yml with `operator create -f operator.yml`. That will install the release-1.0 images.

Comment 3 Roshni 2019-09-13 16:47:34 UTC
Unable to reproduce the issue in the bug description nad migration plan deletion is successful. Verified using the following images.

# oc describe pods/migration-ui-5bf474d9f9-pdxqf -n openshift-migration | grep Image
    Image:          quay.io/ocpmigrate/mig-ui:release-1.0
    Image ID:       quay.io/ocpmigrate/mig-ui@sha256:3af0361dcd85bc55e8040235863caa41b7261c0296ddb53f6926ed9feece1414
# oc describe pods/migration-operator-5cb94b46fb-z7rll -n openshift-migration | grep Image
    Image:         quay.io/ocpmigrate/mig-operator:release-1.0
    Image ID:      quay.io/ocpmigrate/mig-operator@sha256:0bbf26fea92598a65eddbdc1a856de8ee6bee81abdf82231b8e068cd44e41adb
# oc describe pods/controller-manager-78d9589445-sp5jk -n openshift-migration | grep Image
    Image:         quay.io/ocpmigrate/mig-controller:release-1.0
    Image ID:      quay.io/ocpmigrate/mig-controller@sha256:0f74db7171712ffc440b3d7b0f02a775ccd71238827ec856b7d090f90f2feffb

Comment 4 errata-xmlrpc 2019-10-16 06:38:33 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/RHBA-2019:2922


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