Bug 2044973 - [MTC] UI showing “Rollback successful” notification even after a cancelled rollback
Summary: [MTC] UI showing “Rollback successful” notification even after a cancelled ro...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Migration Toolkit for Containers
Classification: Red Hat
Component: UI
Version: 1.7.0
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: 1.7.0
Assignee: Jaydip Gabani
QA Contact: Xin jiang
Steve Goodman
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-01-25 11:53 UTC by ssingla
Modified: 2022-03-24 06:32 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-03-24 06:32:27 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github konveyor mig-controller pull 1260 0 None open Bug 2044973: Making sure that cancel condition gets added to cancelled rollback for UI to display information correctly 2022-01-28 14:29:58 UTC
Github konveyor mig-ui pull 1382 0 None open Bug 2044973: Making sure rollback and stag has correct notifications 2022-02-02 16:15:00 UTC
Red Hat Product Errata RHBA-2022:1043 0 None None None 2022-03-24 06:32:36 UTC

Description ssingla 2022-01-25 11:53:10 UTC
Description of problem:  I executed a rollback from the UI and while it was running, I cancelled it manually.

Severity : Low

Version-Release number of selected component (if applicable): 

MTC 1.7.0
OADP 0.5.5

How reproducible: Always

Steps to reproduce: 

1. Deploy any application inside the source cluster.

2. Login to MTC web console and create a migplan for that application

3. Execute the Migration. 

4. Once the migration is successful, execute the rollback for the same migplan from the MTC UI.

5. Cancel the Rollback manually at any stage.

Actual result: UI shows a notification of “Rollback successful” after cancelling it.
 
Expected result: Rollback should be cancelled and no notification of “Rollback successful” should be displayed.


Additional Info:

migmigration yaml:

apiVersion: migration.openshift.io/v1alpha1
kind: MigMigration
metadata:
  annotations:
    openshift.io/touch: d2f3a93b-7dd3-11ec-bf3b-0a580a820210
  creationTimestamp: "2022-01-25T11:41:51Z"
  generation: 10
  labels:
    migration.openshift.io/migplan-name: test-bugg
    migration.openshift.io/migration-uid: 7ee05786-4c32-422b-b0c6-5d15bb95b055
  name: rollback-c9948
  namespace: openshift-migration
  ownerReferences:
  - apiVersion: migration.openshift.io/v1alpha1
    kind: MigPlan
    name: test-bugg
    uid: fd604115-3803-4154-9042-ee0273293a83
  resourceVersion: "182003"
  uid: 7ee05786-4c32-422b-b0c6-5d15bb95b055
spec:
  canceled: true
  migPlanRef:
    name: test-bugg
    namespace: openshift-migration
  rollback: true
  stage: false
status:
  conditions:
  - category: Advisory
    durable: true
    lastTransitionTime: "2022-01-25T11:42:07Z"
    message: The migration is being canceled.
    reason: Cancel
    status: "True"
    type: Canceling
  - category: Advisory
    durable: true
    lastTransitionTime: "2022-01-25T11:42:07Z"
    message: The migration has completed successfully.
    reason: Completed
    status: "True"
    type: Succeeded
  itinerary: Cancel
  observedDigest: 9f17c9dfc43e85e04e3b92adef4f9cfee575652883d69723da8b857baf9b92ce
  phase: Completed
  pipeline:
  - completed: "2022-01-25T11:41:51Z"
    message: Completed
    name: CleanupVelero
    started: "2022-01-25T11:41:51Z"
  - completed: "2022-01-25T11:41:52Z"
    message: Completed
    name: CleanupHelpers
    started: "2022-01-25T11:41:51Z"
  - completed: "2022-01-25T11:42:07Z"
    message: Completed
    name: CleanupMigrated
    started: "2022-01-25T11:41:52Z"
  - message: Skipped
    name: CleanupUnquiesce
    skipped: true
  - completed: "2022-01-25T11:42:07Z"
    message: Completed
    name: Cleanup
    started: "2022-01-25T11:42:07Z"
  startTimestamp: "2022-01-25T11:41:51Z"

Comment 9 errata-xmlrpc 2022-03-24 06:32:27 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 (Migration Toolkit for Containers (MTC) 1.7.0 release 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-2022:1043


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