-
Bug
-
Resolution: Done-Errata
-
Normal
-
None
-
False
-
-
False
-
oadp-operator-bundle-container-1.3.0-86
-
ToDo
-
-
-
0
-
Very Likely
-
0
-
None
-
Unset
-
Unknown
-
No
Description of problem:
Backup for Mysql application is failing for FileSystemBackup and native Datamover backup.
status: completionTimestamp: "2023-07-31T12:47:23Z" message: 'data path backup failed: Failed to run kopia backup: Error when processing mysql.sock: unknown or unsupported entry type' phase: Failed progress: bytesDone: 52 startTimestamp: "2023-07-31T12:47:22Z"
Version-Release number of selected component (if applicable):
Tested it with velero-datamover feature branch and upstream velero
How reproducible:
always
Steps to Reproduce:
1. Deploy mysql application
$ appm deploy ocp-mysql
2. Execute backup with native datamover
apiVersion: velero.io/v1 kind: Backup metadata: name: test-backup4 labels: velero.io/storage-location: default namespace: velero spec: includedNamespaces: - ocp-mysql snapshotMoveData: true
Actual results:
DataUpload failed with below error
$ oc get dataupload test-backup4-4rm6c -o yaml apiVersion: velero.io/v2alpha1 kind: DataUpload metadata: creationTimestamp: "2023-07-31T12:44:28Z" generateName: test-backup4- generation: 5 labels: velero.io/async-operation-id: du-a6430b29-2976-467c-8ba1-0eece29c5feb.113f789b-f8da-452685525 velero.io/backup-name: test-backup4 velero.io/backup-uid: a6430b29-2976-467c-8ba1-0eece29c5feb velero.io/pvc-uid: 113f789b-f8da-452c-8031-ec28f3d6de3a name: test-backup4-4rm6c namespace: velero ownerReferences: - apiVersion: velero.io/v1 controller: true kind: Backup name: test-backup4 uid: a6430b29-2976-467c-8ba1-0eece29c5feb resourceVersion: "96137" uid: c2f8af7b-14bf-4b0e-8209-c31c1312f89a spec: backupStorageLocation: default csiSnapshot: snapshotClass: "" storageClass: standard-csi volumeSnapshot: velero-mysql-f67rs operationTimeout: 10m0s snapshotType: CSI sourceNamespace: ocp-mysql sourcePVC: mysql status: completionTimestamp: "2023-07-31T12:45:40Z" message: 'data path backup failed: Failed to run kopia backup: Error when processing mysql.sock: unknown or unsupported entry type' node: oadp-48760-h8jkn-worker-b-l48dp.c.openshift-qe.internal phase: Failed progress: {} startTimestamp: "2023-07-31T12:44:28Z"
Expected results:
DataUpload should be successful.
Additional info:
$ cat dpa-minio.yml apiVersion: oadp.openshift.io/v1alpha1 kind: DataProtectionApplication metadata: namespace: openshift-adp name: ts-dpa spec: configuration: restic: enable: true velero: defaultPlugins: - openshift - aws - csi backupLocations: - velero: provider: aws default: true objectStorage: bucket: miniobucket prefix: velero config: insecureSkipTLSVerify: 'true' profile: default region: minio s3ForcePathStyle: 'true' s3Url: http://minio-minio.apps.oadp-48510.qe.devcluster.openshift.com
- links to
-
RHEA-2023:112677
OpenShift API for Data Protection (OADP) 1.3.0 release advisory
[OADP-2360] [Upstream] Kopia backup failing for mysql application
Scott Seago
added a comment - Marking as MODIFIED since the fix is now in our Velero fork. rhn-support-prajoshi I recreated and created an upstream bug, please read through and chime in as you wish 
wnstb Relevant kopia documentation: https://kopia.io/docs/advanced/kopiaignore/#kopiaignore-files
Upstream open issue to support this: https://github.com/vmware-tanzu/velero/issues/4129
sseago spampatt@redhat.com from the related upstream issue 5684, sock files can not be backed up and should be ignored as a result. I'm not sure where the kopia config is for ignored file types, but we should check and ensure .sock is included in that.
ErrorHandlingPolicy is to answer question 3 "An option to simply ignore all files that cannot be backed up (e.g. unix sockets).". That is, a configuration of ErrorHandlingPolicy can tell Kopia uploader to ignore errors.
Additionally the way sock files are being discussed, I would assume it's already in the ignore config but perhaps build in dm does not read the config, just kopia. ¯_(ツ)_/¯
Since the problem described in this issue should be resolved in a recent advisory, it has been closed.
For information on the advisory (Important: OpenShift API for Data Protection (OADP) 1.3.0 security 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:7555