Bug 2231403

Summary: Rsync pod fails to start causing the DVM phase to fail
Product: Migration Toolkit for Containers Reporter: mohamed <midays>
Component: ControllerAssignee: Jason Montleon <jmontleo>
Status: ASSIGNED --- QA Contact: ssingla
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 1.7.12CC: dymurray, rjohnson
Target Milestone: ---   
Target Release: 1.8.4   
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: 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 2023-08-11 13:53:45 UTC
Description of problem:

Some of the migration complete with warnings; the dvm phase fails duw to Rsync pod failing to start, because of a permission issue

Version-Release number of selected component (if applicable):
(GCP) / OCP 3.11 -> 4.14

How reproducible:
Always

Steps to Reproduce:
1. Create a new migration plan
2. Execute migration

Actual results:
The migration fails on the DVM phase, at the end it shows completed with warnings

Expected results:
The migration should be completed successfully

Additional info:
only some of the test cases we executed failed on this, and the connection between them is that all of them required a privileged migration with these labels to be added in the migrated namespace for SCC:

    "pod-security.kubernetes.io/enforce": "privileged",
    "pod-security.kubernetes.io/audit": "privileged",
    "pod-security.kubernetes.io/warn": "privileged"

LOG --------------------------------------

13:23:44.270 - INFO: "category": "Warn",
13:23:44.270 - INFO: "durable": true,
13:23:44.270 - INFO: "lastTransitionTime": "2023-08-10T13:23:31Z",
13:23:44.270 - INFO: "message": "DirectVolumeMigration (dvm): openshift-migration/ocp-24872-mssql-mig-1691673586-jc5qc failed. See in dvm status.Errors",
13:23:44.270 - INFO: "status": "True",
13:23:44.270 - INFO: "type": "DirectVolumeMigrationFailed"
13:23:44.270 - INFO: }

Comment 3 Dylan Murray 2023-08-21 14:49:37 UTC
We are going to defer to documentation around PSA enforcement and SCCs for 1.8, and will work to address better compatibility/validation with PSA in a future release.