Both VMs are synced to the same time server using chronyd.

From: Dennis Kliban [mailto:dkli...@redhat.com]
Sent: May 25, 2022 2:46 PM
To: Briand, Sheldon <sheldon.bri...@nrc-cnrc.gc.ca>
Cc: pulp-list@redhat.com
Subject: Re: [Pulp-list] Error on Azure storage


***ATTENTION*** This email originated from outside of the NRC. ***ATTENTION*** 
Ce courriel provient de l'extérieur du CNRC
Perhaps the time is wrong on the machine trying to download the content?

On Wed, May 25, 2022 at 1:33 PM Briand, Sheldon 
<sheldon.bri...@nrc-cnrc.gc.ca<mailto:sheldon.bri...@nrc-cnrc.gc.ca>> wrote:
Thanks for getting back to me.  The time on the server is correct (it is to the 
eastern time zone).

From: Dennis Kliban [mailto:dkli...@redhat.com<mailto:dkli...@redhat.com>]
Sent: May 25, 2022 2:29 PM
To: Briand, Sheldon 
<sheldon.bri...@nrc-cnrc.gc.ca<mailto:sheldon.bri...@nrc-cnrc.gc.ca>>
Cc: pulp-list@redhat.com<mailto:pulp-list@redhat.com>
Subject: Re: [Pulp-list] Error on Azure storage


***ATTENTION*** This email originated from outside of the NRC. ***ATTENTION*** 
Ce courriel provient de l'extérieur du CNRC
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.bri...@nrc-cnrc.gc.ca<mailto:sheldon.bri...@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@redhat.com<mailto:Pulp-list@redhat.com>
https://listman.redhat.com/mailman/listinfo/pulp-list
_______________________________________________
Pulp-list mailing list
Pulp-list@redhat.com
https://listman.redhat.com/mailman/listinfo/pulp-list

Reply via email to