+++ This bug was initially created as a clone of Bug #2038857 +++ Description of problem: On adding Replication repository to the MTC web console, the repository gets added successfully but after the connection is successful, the “Update Repository” option remains enabled. Version-Release number of selected component (if applicable): MTC 1.6.3 SOURCE CLUSTER: AWS 4.6 MTC 1.6.3 TARGET CLUSTER: AWS 4.9 MTC 1.6.3 How reproducible: Always Steps to reproduce: 1. Login to the MTC web console 2. Go to “Replication repositories” page and Click on “Add replication repository” 3. Fill out the details and Click on “Update Repository” Actual result: Update Repository remains enabled after connection is successful. Expected result: Update Repository should get disabled after the connection check if all the details are same as the previous check and nothing has been updated.
Update button is not getting disabled in case of minio buckets. For AWS S3, GCP and Azure buckets it's working fine. Moving to Assigned status.
Verified with MTC 1.7.2 (Stage) Update button is getting disabled. Moving this to verified status.
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
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 365 days