Bug 2082225 - non-numeric user when launching stage pods [OADP-BL]
Summary: non-numeric user when launching stage pods [OADP-BL]
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Migration Toolkit for Containers
Classification: Red Hat
Component: Velero
Version: 1.7.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 1.7.2
Assignee: Rayford Johnson
QA Contact: Prasad Joshi
Richard Hoch
URL: https://issues.redhat.com/browse/OADP...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-05-05 15:22 UTC by Jason Montleon
Modified: 2022-07-01 09:53 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-07-01 09:53:23 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2022:5483 0 None None None 2022-07-01 09:53:31 UTC

Description Jason Montleon 2022-05-05 15:22:33 UTC 
This is an MTC tracking bug for https://issues.redhat.com/browse/OADP-489

USER nobody:nobody needs to be changed to USER 65534:65534

Upstream links:

https://github.com/openshift/velero/issues/122
https://github.com/openshift/velero/pull/123
https://github.com/vmware-tanzu/velero/issues/2437

The upstream velero-restic-restore-helper image has the fix so if the customer is able to pull from Quay this can be worked around until it is fixed downstream:
```
spec:
  migration_stage_image_fqin: quay.io/konveyor/velero-restic-restore-helper:latest 
```
Comment 6 Prasad Joshi 2022-06-22 13:43:51 UTC 
Verified with MTC 1.7.2 (Stage)

Indirect migrations are working fine with OCP 4.10 and OCP 4.11.

$ oc version
Client Version: 4.7.19
Server Version: 4.11.0-0.nightly-2022-06-22-015220
Kubernetes Version: v1.24.0+284d62a

$ oc get migplan -n openshift-migration -o yaml
  spec:
    destMigClusterRef:
      name: host
      namespace: openshift-migration
    indirectImageMigration: true
    indirectVolumeMigration: true
    migStorageRef:
      name: minio
      namespace: openshift-migration
    namespaces:
    - test-bug
    persistentVolumes:
    - capacity: 1Gi
      name: pvc-34a2c0f8-c8e5-4593-bca0-fcedcd4e3a4b
      proposedCapacity: 1Gi
      pvc:
        accessModes:
        - ReadWriteOnce
        hasReference: true
        name: test-data
        namespace: test-bug
      selection:
        action: copy
        copyMethod: filesystem
        storageClass: standard
      storageClass: standard
      supported:
        actions:
        - skip
        - copy
        copyMethods:
        - filesystem
        - snapshot
    srcMigClusterRef:
      name: source-cluster
      namespace: openshift-migration

$ oc get migmigration -n openshift-migration -o yaml
status:
  conditions:
  - category: Advisory
    durable: true
    lastTransitionTime: "2022-06-22T13:41:07Z"
    message: The migration has completed successfully.
    reason: Completed
    status: "True"
    type: Succeeded

Moving this to verified status.
Comment 12 errata-xmlrpc 2022-07-01 09:53:23 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 (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
Note You need to log in before you can comment on or make changes to this bug.