[Pulp-list] Error on Azure storage

[Dennis Kliban]

I don't have much experience with S3, but is it possible that the date/time
on your Pulp server is not correct?

On Wed, May 25, 2022 at 7:58 AM Briand, Sheldon <
Sheldon.Briand at nrc-cnrc.gc.ca> wrote:

> Hi,
>
>
>
> I’m getting an error when I’m accessing Azure storage for a AlmaLinux 8
> pulp repository.
>
>
>
> From the dnf.log:
>
> error: Status code: 403 for
> https://xxxxxxxxxxxxxxxxxxxxxx/pulp-storage/artifact/37/e8d520f7f51a02ddddb3530d1e51
>
>
> cc1b74e9b9f10c46c358ed78cca91ddba0?se=2022-05-23T20%3A01%3A52Z&sp=rt&sv=2021-04-
>
> 10
>
>
>
> The above error doesn’t show it but it includes a signature (I have
> purposely put xxxxxxx in for the storage account address).
>
>
>
> If I try to manually run the above query with curl and the URL in quotes I
> get:
>
> ERROR 403: Server failed to authenticate the request. Make sure the value
> of Authorization header is formed correctly including the signature..
>
> </Message><AuthenticationErrorDetail>Signed expiry time [Wed, 25 May 2022
> 09:51:09 GMT] must be after signed start time [Wed, 25 May 2022 10:00:16
> GMT]</AuthenticationErrorDetail></Error>
>
>
>
> I ran a cron job which generated this error in the logs.  The cron job ran
> at Wed, 25 May 2022 09:56:00 GMT.  So to me it looks like the expiry time
> is set to a time before the request is even made and that gives me the 403
> error.  Is this a possible bug?
>
>
>
> Thanks,
>
> -Sheldon
> _______________________________________________
> Pulp-list mailing list
> Pulp-list at redhat.com
> https://listman.redhat.com/mailman/listinfo/pulp-list
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/pulp-list/attachments/20220525/c244544a/attachment.htm>