+++ This bug was initially created as a clone of Bug #2073488 +++ Description of problem: Any error happening during creation of Rsync pods does not get printed in the controller logs Version-Release number of selected component (if applicable): 1.6.0 How reproducible: Always Steps to Reproduce: 1. Deploy any sample application in source namespace 2. Create a ResourceQuota (after creating application) so that no new Pods can be created in the source namespace: ```yaml apiVersion: v1 kind: ResourceQuota metadata: name: zero-pod-quota namespace: rocket-chat spec: hard: pods: "0" ``` 3. Create a migration plan for above namespace and select DVM 4. Run a Stage/Cutover migration, and observe that it will get stuck at DirectVolume step with message "Running Rsync Pods to migrate Persistent Volume data" Actual results: The migration gets stuck, there are no logs in the controller pertaining to creation of Pods. Expected results: Migration getting stuck is expected, but there should be some logs explaining the actual error in Pod creation. Additional info:
*** Bug 2073494 has been marked as a duplicate of this bug. ***
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.1 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:1734