Bug Report: Incorrect Path Appended to S3 Bucket During Backup Causes Path Not Found Error #2089
Description
Bug Report: Incorrect Path Appended to S3 Bucket During Backup Causes Path Not Found Error
Description
When performing a backup, an extra path is automatically appended after my S3 bucket name, which leads to an error stating that the path cannot be found. This appears to be an issue with how the backup tool constructs the S3 path.
Configuration
s3:
bucket: repo/cloud-db-backup/mysql
credentialsSecret: cluster-name-backup-s3
region: oss-cn-hangzhou
endpointUrl: https://repo.oss-cn-hangzhou.aliyuncs.comRelevant Logs
xtrabackup + local is_deleted_full=0
xtrabackup + local is_deleted_info=0
xtrabackup + for i in {1..5}
xtrabackup + (( i > 1 ))
xtrabackup + is_object_exist repo cloud-db-backup/mysql/cluster1-2025-06-10-07:20:10-full/
xtrabackup + local bucket=repo
xtrabackup + local path=cloud-db-backup/mysql/cluster1-2025-06-10-07:20:10-full/
xtrabackup ++ aws --no-verify-ssl s3 ls s3://repo/cloud-db-backup/mysql/cluster1-2025-06-10-07:20:10-full/ --summarize --recursive
xtrabackup urllib3/connectionpool.py:1064: InsecureRequestWarning: Unverified HTTPS request is being made to host 'wg-repo.tronclass.com.cn'. Adding certificate verification is strongly advised.
xtrabackup
xtrabackup An error occurred (NoSuchKey) when calling the ListObjectsV2 operation: The specified key does not exist.
xtrabackup + res=
xtrabackup + echo ''
xtrabackup + grep -q 'Total Objects: 0'
xtrabackup + return 0
xtrabackup + log INFO 'Delete (attempt 1)...'
xtrabackup 2025-06-10 07:20:35 [INFO] Delete (attempt 1)...
xtrabackup + xbcloud delete --insecure --curl-retriable-errors=7 --storage=s3 --s3-bucket=repo cloud-db-backup/mysql/cluster1-2025-06-10-07:20:10-full
xtrabackup error: http request failed: Couldn't resolve host name
xtrabackup error: http request failed: Couldn't resolve host name
xtrabackup 250610 07:20:35 xbcloud: Successfully connected.
Steps to Reproduce
- Configure S3 backup with the provided configuration.
- Start a backup operation.
- Observe that the path constructed appends an additional path segment after the bucket name.
- Notice the error indicating the specified key/path does not exist.
Expected Behavior
The backup tool should use the correct S3 path without appending extra directories or segments, so that the backup and deletion operations can locate the correct objects in the bucket.
Actual Behavior
An additional path is appended after the bucket name, resulting in a "NoSuchKey" error and failed operations.
Environment
- Backup tool: xtrabackup/xbcloud
- S3 provider: Aliyun OSS
- Region: oss-cn-hangzhou
Additional Information
- The issue seems related to how the bucket and path are concatenated in the backup script or tool.
- Please advise if additional logs or configuration details are needed.
Thank you for your help!