Bug 2212528 - Rsync pod fails due to error in starting client-server protocol (code 5)
Summary: Rsync pod fails due to error in starting client-server protocol (code 5)
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Migration Toolkit for Containers
Classification: Red Hat
Component: Controller
Version: 1.7.10
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
: 1.7.10
Assignee: Pranav Gaikwad
QA Contact: ssingla
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-06-05 19:52 UTC by mohamed
Modified: 2023-06-15 09:50 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-06-15 09:48:27 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github migtools mig-controller pull 1346 0 None Merged Bump crane-lib (#1345) 2023-06-07 19:30:05 UTC
Red Hat Product Errata RHSA-2023:3624 0 None None None 2023-06-15 09:50:02 UTC

Description mohamed 2023-06-05 19:52:54 UTC
Description of problem:

Direct migration fails at DVM phase due to error in rsync pod, it fails to start client-server protocol 

Version-Release number of selected component (if applicable):
MTC 1.7.10
OCP 3.11 -> OCP 4.6

How reproducible:
Always

Steps to Reproduce:
1. Create a new project and deploy an app in it
2. Create a new migration plan 
3. Run the migration

Actual results:
Migration completes with warnings, it fails at DVM phase

Expected results:
The migration should be completed without any warnings or errors

Additional info:

from the rsync pod logs:

[midays@fedora ~]$ oc -n django logs -f rsync-qxwl6 
Defaulted container "rsync" out of: rsync, stunnel
2023/06/05 18:59:14 [28] @ERROR: chroot failed
2023/06/05 18:59:14 [28] rsync error: error starting client-server protocol (code 5) at main.c(1668) [sender=3.1.3]
@ERROR: chroot failed
rsync error: error starting client-server protocol (code 5) at main.c(1668) [sender=3.1.3]

MigrationController CR:

apiVersion: v1
items:
- apiVersion: migration.openshift.io/v1alpha1
  kind: MigrationController
  metadata:
    creationTimestamp: "2023-06-05T17:37:04Z"
    generation: 3
    name: migration-controller
    namespace: openshift-migration
    resourceVersion: "101527"
    selfLink: /apis/migration.openshift.io/v1alpha1/namespaces/openshift-migration/migrationcontrollers/migration-controller
    uid: 3ea0d8e3-0525-4355-97b5-2ce2c440e78b
  spec:
    azure_resource_group: ""
    cluster_name: host
    mig_namespace_limit: "10"
    mig_pod_limit: "100"
    mig_pv_limit: "100"
    migration_controller: true
    migration_log_reader: true
    migration_ui: true
    migration_velero: true
    olm_managed: true
    restic_timeout: 1h
    version: 1.7.10
  status:
    conditions:
    - lastTransitionTime: "2023-06-05T18:02:53Z"
      message: ""
      reason: ""
      status: "False"
      type: Failure
    - ansibleResult:
        changed: 0
        completion: 2023-06-05T19:32:47.050794
        failures: 0
        ok: 51
        skipped: 22
      lastTransitionTime: "2023-06-05T18:02:53Z"
      message: Awaiting next reconciliation
      reason: Successful
      status: "True"
      type: Running
    - lastTransitionTime: "2023-06-05T19:32:47Z"
      message: Last reconciliation succeeded
      reason: Successful
      status: "True"
      type: Successful
kind: List
metadata:
  resourceVersion: ""

Comment 9 errata-xmlrpc 2023-06-15 09:48:27 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 (Important: Migration Toolkit for Containers (MTC) 1.7.10 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-2023:3624


Note You need to log in before you can comment on or make changes to this bug.