| Bug #114696 | deleteBackupData not work when delete mbk cr | ||
|---|---|---|---|
| Submitted: | 19 Apr 2024 3:43 | Modified: | 7 May 2024 7:33 |
| Reporter: | Bing Ma (OCA) | Email Updates: | |
| Status: | Verified | Impact on me: | |
| Category: | MySQL Operator | Severity: | S3 (Non-critical) |
| Version: | 8.3.0-2.1.2 | OS: | Any |
| Assigned to: | CPU Architecture: | Any | |
[19 Apr 2024 8:19]
Bing Ma
in this link https://dev.mysql.com/doc/mysql-operator/en/mysql-operator-properties.html
[7 May 2024 7:33]
MySQL Verification Team
Thanks for the report
Description: Is it that I'm not using it correctly, or is there a bug? When I deleted the MBK resources, the backup files in Minio were not removed. ###### spec: addTimestampToBackupDirectory: true backupProfile: dumpInstance: storage: s3: bucketName: mabing config: mgr0416-mgr-auto-secret-copy endpoint: http://my_ip:80 prefix: /aaaa profile: "" name: test0419 clusterName: mgr0416 deleteBackupData: true How to repeat: use this spec ###### spec: addTimestampToBackupDirectory: true backupProfile: dumpInstance: storage: s3: bucketName: mabing config: mgr0416-mgr-auto-secret-copy endpoint: http://my_ip:80 prefix: /aaaa profile: "" name: test0419 clusterName: mgr0416 deleteBackupData: true ###### kubectl get mbk NAME CLUSTER STATUS OUTPUT AGE test0419 mgr0416 Completed test0419-20240419-033716 3m15sv ###### kubectl delete mbk test0419 mysqlbackup.mysql.oracle.com "test0419" deleted the backup data still exist in S3