Bug 2073494

Summary: Errors in rsync pod creation are not printed in the controller logs
Product: Migration Toolkit for Containers Reporter: Pranav Gaikwad <pgaikwad>
Component: ControllerAssignee: Erik Nelson <ernelson>
Status: CLOSED DUPLICATE QA Contact: Xin jiang <xjiang>
Severity: medium Docs Contact: Richard Hoch <rhoch>
Priority: unspecified    
Version: 1.7.0CC: ernelson, rhoch, xjiang
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 2073488 Environment:
Last Closed: 2022-04-08 15:44:42 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Pranav Gaikwad 2022-04-08 15:37:33 UTC 
+++ 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: