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:
Confirmed with Maayan on mig05 environment. There is still an issue in UI-executed must-gather targeted to non-existing VM (Plan is OK). Since VM and relared CRs are missing, the process of gathering logs should be stopped instead of providing not relevant files with grep/gathering logs error. Will work on this.
https://github.com/konveyor/forklift-must-gather/pull/41
Backported to 2.3 by https://github.com/konveyor/forklift-must-gather/pull/43
Fixed in MTV-2.3.0-30 Index image v4.9: iib:177398 Index image v4.10: iib:177400
Verified on MTV 2.3.0-37, if particular resource is missing - respective log file just doesn't exist in the archive, LGTM
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 (MTV 2.3.0 images), 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-2022:1183