Bug 2023764 - Logs archive file downloaded from UI includes logs related to deleted migration plan/VM
Summary: Logs archive file downloaded from UI includes logs related to deleted migrati...
Keywords:
Status: ASSIGNED
Alias: None
Product: Migration Toolkit for Virtualization
Classification: Red Hat
Component: User Experience
Version: 2.2.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 2.3.0
Assignee: Marek Aufart
QA Contact: Maayan Hadasi
Avital Pinnick
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-11-16 13:26 UTC by Maayan Hadasi
Modified: 2021-11-16 17:00 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:


Attachments (Terms of Use)

Description Maayan Hadasi 2021-11-16 13:26:18 UTC
Description of problem:
In the following cases - the logs file downloaded from UI may contain logs that are related to a previous migration plan:
- Delete migration plan and recreate a new one with the same name
- Delete migrated VM on destination side and re-migrate it using a new migration plan
In those cases - there is no 'Get logs' button at the end of migration, but immediately 'Download logs' button is enabled


Version-Release number of selected component (if applicable):
MTV 2.2.0-84 / iib:133381


How reproducible:
Not always


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Marek Aufart 2021-11-16 13:36:17 UTC
Thanks for reporting this issue! There is a custom-name used to pair must-gather execution with the object that the "Get logs" button was clicked. This custom name is set by UI and currently it is plan's or VM's name (as agreed between me and Mike-s).

I'd suggest add deletion of related must-gather executions to UI delete action of the Plan. That should fix at least the UI Plan deletion. "Long-time" deletion of archives is configured in must-gather-api service using existing CLEANUP_MAX_AGE config option.


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