36
> --
> *From:* Mike DePaulo
> *Sent:* 09 November 2019 13:47
> *To:* David Davis
> *Cc:* Dumont, Joey; pulp-list@redhat.com
> *Subject:* Re: [Pulp-list] Issues with using S3 storage when running pulp
> on Amazon EC2 (pulp3)
>
> I think that wi
Sent: 09 November 2019 13:47
To: David Davis
Cc: Dumont, Joey; pulp-list@redhat.com
Subject: Re: [Pulp-list] Issues with using S3 storage when running pulp on
Amazon EC2 (pulp3)
I think that with Ansible syntax, you need to specify:
AWS_DEFAULT_ACL:
I am fairly certain the lack of any value a
dvisor, Knowledge, Information, and Technology Services
>> National Research Council Canada / Governement of Canada
>> joey.dum...@nrc-cnrc.gc.ca / Tel: 613-990-8152 / Cell: 438-340-7436
>>
>> Conseiller technique, Services du savoir, de l'information et de la
>>
ist-boun...@redhat.com on
> behalf of Dumont, Joey
> *Sent:* 06 November 2019 11:36
> *To:* Mike DePaulo
> *Cc:* pulp-list@redhat.com
> *Subject:* Re: [Pulp-list] Issues with using S3 storage when running pulp
> on Amazon EC2 (pulp3)
>
>
> PR, as suggested: https://
nrc-cnrc.gc.ca<mailto:joey.dum...@nrc-cnrc.gc.ca> / Tél.:
613-990-8152 / Tél. cell.: 438-340-7436
From: Mike DePaulo
Sent: 06 November 2019 10:52
To: Dumont, Joey
Cc: David Davis; pulp-list@redhat.com
Subject: Re: [Pulp-list] Issues with using S3 storage when ru
ll.: 438-340-7436
From: Mike DePaulo
Sent: 06 November 2019 10:52
To: Dumont, Joey
Cc: David Davis; pulp-list@redhat.com
Subject: Re: [Pulp-list] Issues with using S3 storage when running pulp on
Amazon EC2 (pulp3)
Hi Joey,
It sounds like aws_default_acl should be documented
90-8152 / Tél. cell.: 438-340-7436
> --
> *From:* David Davis
> *Sent:* 01 November 2019 15:51
> *To:* Dumont, Joey
> *Cc:* pulp-list@redhat.com
> *Subject:* Re: [Pulp-list] Issues with using S3 storage when running pulp
> on Amazon EC2 (pulp3)
>
&g
__
From: David Davis
Sent: 01 November 2019 15:51
To: Dumont, Joey
Cc: pulp-list@redhat.com
Subject: Re: [Pulp-list] Issues with using S3 storage when running pulp on
Amazon EC2 (pulp3)
Unfortunately I don't know of a good way to debug the problem other than to dig
into the
Unfortunately I don't know of a good way to debug the problem other than to
dig into the code. If you want to debug from the Pulp code, you could stick
a debugger in the artifact saver stage:
https://github.com/pulp/pulpcore/blob/2203fee1407738a4ddd8e644fcbc741aab0bca63/pulpcore/plugin/stages/arti
