[Pulp-list] sync issue on 3.7.3

Dennis Kliban dkliban at redhat.com
Mon Nov 2 19:10:35 UTC 2020


Are both systems downloading via the same proxy?

Could you share the output of 'pip freeze' from your 3.7.3 install and one
from your 3.3 install?

On Mon, Nov 2, 2020 at 11:13 AM Bin Li (BLOOMBERG/ 120 PARK) <
bli111 at bloomberg.net> wrote:

> We have been seeing a few sync issues during test of 3.7.3. Below is a
> list of summary of repo name and errors. We were able to resolve some
> issues by rerun the sync but most of errors seems to be consistent. The
> test was done on a 4cpu 64GB host with 2 workers configured. We are running
> 3.3 in our production without any of these issue. Just wondering if anyone
> experienced something similar and how we troubleshoot.
>
>
> rhel-7-server-optional-rpms
> Response payload is not completed
> =========
> rhel-7-server-rpms
> Cannot connect to host cdn.redhat.com:443 ssl:default [Connection reset
> by peer]
> =========
> rhel-7-server-debug-rpms
> Cannot connect to host cdn.redhat.com:443 ssl:default [None]
> =========
> rhel-7-server-source-rpms
> [Errno 104] Connection reset by peer
> =========
> rhel-server-rhscl-7-rpms
> Response payload is not completed
> =========
> rhel-7-server-optional-debug-rpms
> Response payload is not completed
>
> _______________________________________________
> Pulp-list mailing list
> Pulp-list at redhat.com
> https://www.redhat.com/mailman/listinfo/pulp-list
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/pulp-list/attachments/20201102/46ae3f8b/attachment.htm>


More information about the Pulp-list mailing list