Closed DnPlas closed 2 months ago
confirmed that the provided endpoint had the bucket name which caused the above issue:
https://<bucket-name>.s3.<region-name>.amazonaws.com
was used
https://s3.<region-name>.amazonaws.com
should be used
the below is output after the corrected endpoint is used:
(venv) ubuntu@localhost:~$ juju run mysql/leader list-backups
Running operation 21 with 1 task
- task 22 on unit-mysql-0
Waiting for task 22...
backups: |-
backup-id | backup-type | backup-status
----------------------------------------------------
(venv) ubuntu@localhost:~$ juju run mysql/leader create-backup
Running operation 23 with 1 task
- task 24 on unit-mysql-0
Waiting for task 24...
backup-id: "2024-04-25T16:05:39Z"
(venv) ubuntu@localhost:~$ juju run mysql/leader list-backups
Running operation 25 with 1 task
- task 26 on unit-mysql-0
Waiting for task 26...
backups: |-
backup-id | backup-type | backup-status
----------------------------------------------------
2024-04-25T16:05:39Z | physical | finished
I can confirm that the commands succeed after fixing the endpoint, thanks! Closing this as there is no issue with the charm.
Steps to reproduce
kfp-db
=mysql-k8s
This created a new folder in my s3 named daniela-bucket-1 (same as the name I passed in the config), then inside it, there is another folder named backup-folder (same as the name I passed in the config). Inside backup-folder I see backup.log and metadata files.
I would not expect the action to create a new folder(s) in my s3 bucket.
The tree in my s3 looks like this:
Amazon S3 > Buckets > daniela-bucket-1 > daniela-bucket-1/ > backup-folder
Expected behavior
Actual behavior
backup
action creates new folders in my s3list-backups
returns an error (see above)Versions
Operating system: ubuntu 22.04
Juju CLI: 3.1/stable
Juju agent: 3.1
Charm revision: 8.0/stable
microk8s: 1.25-strict/stable
Log output
Added above.