<div dir="ltr"><div>What version of django-storages do you have installed? Could you try downgrading it to 1.11.1? Don't forget to restart pulpcore-content services after. </div><div> </div><div>I found a not completely related issue[0] with django-storages newer than 1.11.1. </div><div> </div><div>[0] <a href="https://github.com/jschneier/django-storages/issues/1116">https://github.com/jschneier/django-storages/issues/1116</a></div></div> <div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, May 25, 2022 at 1:47 PM Briand, Sheldon <<a href="mailto:Sheldon.Briand@nrc-cnrc.gc.ca">Sheldon.Briand@nrc-cnrc.gc.ca</a>> wrote: </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> <div lang="EN-CA"> <div class="gmail-m_-875569637969724863WordSection1"> Both VMs are synced to the same time server using chronyd. <div> <div style="border-color:rgb(225,225,225) currentcolor currentcolor;border-style:solid none none;border-width:1pt medium medium;padding:3pt 0cm 0cm"> From: Dennis Kliban [mailto:<a href="mailto:dkliban@redhat.com" target="_blank">dkliban@redhat.com</a>] Sent: May 25, 2022 2:46 PM To: Briand, Sheldon <<a href="mailto:Sheldon.Briand@nrc-cnrc.gc.ca" target="_blank">Sheldon.Briand@nrc-cnrc.gc.ca</a>> Cc: <a href="mailto:pulp-list@redhat.com" target="_blank">pulp-list@redhat.com</a> Subject: Re: [Pulp-list] Error on Azure storage </div> </div> ***ATTENTION*** This email originated from outside of the NRC. ***ATTENTION*** Ce courriel provient de l'extérieur du CNRC <div> <div> Perhaps the time is wrong on the machine trying to download the content? </div> <div> <div> On Wed, May 25, 2022 at 1:33 PM Briand, Sheldon <<a href="mailto:Sheldon.Briand@nrc-cnrc.gc.ca" target="_blank">Sheldon.Briand@nrc-cnrc.gc.ca</a>> wrote: </div> <blockquote style="border-color:currentcolor currentcolor currentcolor rgb(204,204,204);border-style:none none none solid;border-width:medium medium medium 1pt;padding:0cm 0cm 0cm 6pt;margin-left:4.8pt;margin-right:0cm"> <div> <div> Thanks for getting back to me. The time on the server is correct (it is to the eastern time zone). <div> <div style="border-style:solid none none;border-width:1pt medium medium;padding:3pt 0cm 0cm;border-color:currentcolor"> From: Dennis Kliban [mailto:<a href="mailto:dkliban@redhat.com" target="_blank">dkliban@redhat.com</a>] Sent: May 25, 2022 2:29 PM To: Briand, Sheldon <<a href="mailto:Sheldon.Briand@nrc-cnrc.gc.ca" target="_blank">Sheldon.Briand@nrc-cnrc.gc.ca</a>> Cc: <a href="mailto:pulp-list@redhat.com" target="_blank">pulp-list@redhat.com</a> Subject: Re: [Pulp-list] Error on Azure storage </div> </div> ***ATTENTION*** This email originated from outside of the NRC. ***ATTENTION*** Ce courriel provient de l'extérieur du CNRC <div> <div> I don't have much experience with S3, but is it possible that the date/time on your Pulp server is not correct? </div> <div> <div> On Wed, May 25, 2022 at 7:58 AM Briand, Sheldon <<a href="mailto:Sheldon.Briand@nrc-cnrc.gc.ca" target="_blank">Sheldon.Briand@nrc-cnrc.gc.ca</a>> wrote: </div> <blockquote style="border-style:none none none solid;border-width:medium medium medium 1pt;padding:0cm 0cm 0cm 6pt;margin:5pt 0cm 5pt 4.8pt;border-color:currentcolor currentcolor currentcolor rgb(204,204,204)"> <div> <div> 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 <a href="https://xxxxxxxxxxxxxxxxxxxxxx/pulp-storage/artifact/37/e8d520f7f51a02ddddb3530d1e51" target="_blank"> https://xxxxxxxxxxxxxxxxxxxxxx/pulp-storage/artifact/37/e8d520f7f51a02ddddb3530d1e51</a> 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 </div> </div> _______________________________________________ Pulp-list mailing list <a href="mailto:Pulp-list@redhat.com" target="_blank">Pulp-list@redhat.com</a> <a href="https://listman.redhat.com/mailman/listinfo/pulp-list" target="_blank">https://listman.redhat.com/mailman/listinfo/pulp-list</a> </blockquote> </div> </div> </div> </div> </blockquote> </div> </div> </div> </div> </blockquote></div>