Thanks. Here is the info On Test Server with 3.7.3# pip freeze aiodns==2.0.0 aiofiles==0.6.0 aiohttp==3.7.2 ansible==2.10.1 ansible-base==2.10.2 async-timeout==3.0.1 attrs==20.2.0 backoff==1.10.0 certifi==2020.6.20 cffi==1.14.3 chardet==3.0.4 click==7.1.2 coreapi==2.3.3 coreschema==0.0.4 createrepo-c==0.16.0.post1 cryptography==3.2.1 defusedxml==0.6.0 diff-match-patch==20200713 distro==1.5.0 Django==2.2.16 django-currentuser==0.5.1 django-extensions==3.0.9 django-filter==2.3.0 django-guardian==2.3.0 django-import-export==2.3.0 django-lifecycle==0.8.0 django-readonly-field==1.0.5 djangorestframework==3.11.2 djangorestframework-queryfields==1.0.0 drf-access-policy==0.7.0 drf-nested-routers==0.91 drf-spectacular==0.9.13 drf-yasg==1.17.1 dynaconf==3.1.2 et-xmlfile==1.0.1 gunicorn==20.0.4 idna==2.10 importlib-metadata==2.0.0 inflection==0.5.1 itypes==1.2.0 jdcal==1.4.1 Jinja2==2.11.2 jsonschema==3.2.0 libcomps==0.1.15.post1 MarkupPy==1.14 MarkupSafe==1.1.1 modulemd==1.3.3 multidict==5.0.0 nose==1.3.7 odfpy==1.4.1 openpyxl==3.0.5 packaging==20.4 pip-tools==5.3.1 productmd==1.28 psycopg2==2.8.6 pulp-file==1.3.0 pulp-file-client==1.3.0 pulp-rpm==3.7.0 pulp-rpm-client==3.7.0 pulpcore==3.7.3 pulpcore-client==3.7.3 pyasn1==0.4.8 pyasn1-modules==0.2.8 pycairo==1.20.0 pycares==3.1.1 pycparser==2.20 PyGObject==3.38.0 pygtrie==2.3.3 pyparsing==2.4.7 pyrsistent==0.17.3 python-box==5.2.0 python-dateutil==2.8.1 python-dotenv==0.15.0 python-gnupg==0.4.6 python-ldap==3.3.1 pytz==2020.1 PyYAML==5.3.1 redis==3.5.3 requests==2.24.0 rq==1.3.0 ruamel.yaml==0.16.12 ruamel.yaml.clib==0.2.2 scikit-build==0.11.1 six==1.15.0 solv==0.7.14 sqlparse==0.4.1 tablib==2.0.0 toml==0.10.1 typing-extensions==3.7.4.3 uritemplate==3.0.1 urllib3==1.25.11 urlman==1.3.0 whitenoise==5.0.1 xlrd==1.2.0 xlwt==1.3.0 yarl==1.6.2 zipp==3.4.0
On Prod server running 3.3 aiodns==2.0.0 aiofiles==0.5.0 aiohttp==3.6.2 ansible==2.9.9 async-timeout==3.0.1 attrs==19.3.0 autopep8==1.5.3 backoff==1.10.0 certifi==2020.4.5.1 cffi==1.14.0 chardet==3.0.4 click==7.1.2 coreapi==2.3.3 coreschema==0.0.4 createrepo-c==0.15.10 cryptography==2.9.2 defusedxml==0.6.0 diff-match-patch==20181111 distro==1.5.0 Django==2.2.12 django-filter==2.2.0 django-import-export==2.0.2 djangorestframework==3.10.3 djangorestframework-queryfields==1.0.0 drf-nested-routers==0.91 drf-yasg==1.17.1 dynaconf==3.0.0rc1 et-xmlfile==1.0.1 gunicorn==20.0.4 idna==2.9 importlib-metadata==1.6.0 inflection==0.4.0 itypes==1.2.0 jdcal==1.4.1 Jinja2==2.11.2 jsonschema==3.2.0 libcomps==0.1.14.post1 MarkupPy==1.14 MarkupSafe==1.1.1 modulemd==1.3.3 multidict==4.7.6 nose==1.3.7 odfpy==1.4.1 openpyxl==3.0.3 packaging==20.4 pip-tools==5.2.0 productmd==1.26 psycopg2==2.8.5 pulp-file==0.3.0 pulp-file-client==0.3.0 pulp-rpm==3.3.2 pulp-rpm-client==3.3.2 pulpcore==3.3.1 pulpcore-client==3.3.1 pyasn1==0.4.8 pyasn1-modules==0.2.8 pycairo==1.19.1 pycares==3.1.1 pycodestyle==2.6.0 pycparser==2.20 PyGObject==3.36.1 pygtrie==2.3.3 pyparsing==2.4.7 pyrsistent==0.16.0 python-box==4.2.3 python-dateutil==2.8.1 python-dotenv==0.13.0 python-gnupg==0.4.6 python-ldap==3.2.0 pytz==2020.1 PyYAML==5.3.1 redis==3.5.2 requests==2.23.0 rq==1.3.0 ruamel.yaml==0.16.10 ruamel.yaml.clib==0.2.0 scikit-build==0.11.1 six==1.15.0 solv==0.7.11 sqlparse==0.3.1 tablib==2.0.0 toml==0.10.1 uritemplate==3.0.1 urllib3==1.25.9 whitenoise==5.0.1 xlrd==1.2.0 xlwt==1.3.0 yarl==1.4.2 zipp==3.1.0 They are on different proxy host. I am asking network team to check proxy also. From: [email protected] At: 11/02/20 14:10:53To: Bin Li (BLOOMBERG/ 120 PARK ) Cc: [email protected] Subject: Re: [Pulp-list] sync issue on 3.7.3 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) <[email protected]> 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 [email protected] https://www.redhat.com/mailman/listinfo/pulp-list
_______________________________________________ Pulp-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/pulp-list
