You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Run the backups integration test: tox -e integration -- tests/integration/test_backups.py::test_backup_aws --keep-models
Encounter botocore.exceptions.ClientError error
Expected behavior
Test to successfully complete.
Actual behavior
Test fails with ERROR tests/integration/test_backups.py::test_backup_aws - botocore.exceptions.ClientError: An error occurred (SignatureDoesNotMatch) when calling the ListObjects operation: Access denied.
Versions
Operating system: Ubuntu 24.04.1 LTS
Juju CLI: 3.5.3-genericlinux-amd64 (also tried 3.4.x, but same result)
Juju agent: 3.5.3 (also tried 3.4.x, but same result)
Charm revision: 5a89a40 (latest commit). Also tried rev371 as of 30.08.2024, but same result.
microk8s: MicroK8s v1.31.1 revision 7234 (tried 1.30, 1.29 with the same result)
The issue is caused by the GCP credentials not being present in the SECRETS_FROM_GITHUB environment variable; the test teardown code is trying to list objects from GCS (as well as from AWS) at
Steps to reproduce
tox -e integration -- tests/integration/test_backups.py::test_backup_aws --keep-models
botocore.exceptions.ClientError
errorExpected behavior
Test to successfully complete.
Actual behavior
Test fails with
ERROR tests/integration/test_backups.py::test_backup_aws - botocore.exceptions.ClientError: An error occurred (SignatureDoesNotMatch) when calling the ListObjects operation: Access denied.
Versions
Operating system: Ubuntu 24.04.1 LTS
Juju CLI: 3.5.3-genericlinux-amd64 (also tried 3.4.x, but same result)
Juju agent: 3.5.3 (also tried 3.4.x, but same result)
Charm revision: 5a89a40 (latest commit). Also tried rev371 as of 30.08.2024, but same result.
microk8s: MicroK8s v1.31.1 revision 7234 (tried 1.30, 1.29 with the same result)
Log output
Juju debug log: k8s_SignatureDoesNotMatch.log
Additional context
Same issue on the VM: canonical/postgresql-operator#635.
The text was updated successfully, but these errors were encountered: