Bug 2023260 - [Targeted must-gather] Handling not-existing MTV resources before logs collection
Summary: [Targeted must-gather] Handling not-existing MTV resources before logs collec...
Keywords:
Status: ASSIGNED
Alias: None
Product: Migration Toolkit for Virtualization
Classification: Red Hat
Component: Must-Gather
Version: 2.2.0
Hardware: Unspecified
OS: Unspecified
high
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-15 10:31 UTC by Maayan Hadasi
Modified: 2022-01-10 07:16 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-15 10:31:31 UTC
Description of problem:
In case that a resource does not exist - there should be an appropriate message or not to collect the yaml/log of that resource
For example, when the virt-launcher pod does not exist because the destination VM is not running, the following unexpected log is present in the archive logs file, downloaded from UI:

[mguetta@localhost must-gather]$ cat ./namespaces/openshift-mtv/logs/current.log
error: expected 'logs [-f] [-p] (POD | TYPE/NAME) [-c CONTAINER]'.
POD or TYPE/NAME is a required argument for the logs command
See 'oc logs -h' for help and examples


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


How reproducible:
100%


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:


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