Errors publishing to GCP and Azure

Open scentoni opened this issue 9 months ago • 1 comments

Hi folks,

Besides seeing performance problems on AWS S3 as described in https://github.com/aptly-dev/aptly/issues/1433 and https://github.com/aptly-dev/aptly/issues/1435, we find replacing Aptly 1.5.0 with Aptly 1.6.1 leads to an immediate failure when we publish to GCP via the S3 protocol:

ERROR: unable to publish: unable to process packages: error caching paths under prefix: failed to get page 1: operation error S3: ListObjectsV2, https response error StatusCode: 403, RequestID: , HostID: , api error SignatureDoesNotMatch: Access denied.
ERROR: Publish switch to new snapshot SNAPSHOT to s3:BUCKET:amd64 with dist focal failed!

We also see an error with publishing to Azure, but this occurs about an hour after the beginning of the publishing:

ERROR: unable to publish: unable to rename: error acquiring lease on source blob amd64/dists/focal/main/binary-amd64/Packages.tmp.bz2
ERROR: Publish switch to new snapshot SNAPSHOT to azure:BUCKET:amd64 with dist focal failed!

Apr 04 '25 00:04 scentoni

Thanks @scentoni for reporting.

could you share your S3/Azure config (except credentials) ?

The first problem looks like missing permissions in S3, and there was a change with the default permissions... We will try to reproduce the problem, but would need some help from your side.

Apr 21 '25 11:04 neolynx