Bug 2076593

Summary: Velero pod log missing from UI drop down
Product: Migration Toolkit for Containers Reporter: mohamed <midays>
Component: UIAssignee: Jaydip Gabani <jgabani>
Status: CLOSED ERRATA QA Contact: ssingla
Severity: low Docs Contact: Richard Hoch <rhoch>
Priority: low    
Version: 1.7.1CC: rjohnson
Target Milestone: ---   
Target Release: 1.7.2   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-07-01 09:53:11 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description mohamed 2022-04-19 12:55:01 UTC
Description of problem: After a migration is executed, the velero pod log is not included in the logs provided in the dropdown list.

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

How reproducible:
always

Steps to Reproduce:
1. create a migration plan
2. execute the migration
3. click on the three dots on the right side of the migraiton, and select logs
4. select a cluster (source or target) 
5. click on the drop down list beside the Select Pod Source label 

Actual results: the velero pod log is not shown in the list


Expected results: the velero pod log shouyld be displayed and selectable


Additional info:

Comment 6 ssingla 2022-06-16 08:49:22 UTC
Verified with MTC 1.7.2 prestage


-------
Select cluster:

destination

Select Pod Source:


velero-6d695dc988-snwsr-velero

-----------

Comment 12 errata-xmlrpc 2022-07-01 09:53:11 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 (Moderate: Migration Toolkit for Containers (MTC) 1.7.2 security and bug fix update), 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/RHSA-2022:5483