Pulp: Issueshttps://pulp.plan.io/https://pulp.plan.io/favicon.ico2020-12-02T11:24:03ZPulp
Planio Nectar - Issue #7911 (MODIFIED): Unable to sync large openshift docker reposhttps://pulp.plan.io/issues/79112020-12-02T11:24:03Zipanova@redhat.comipanova@redhat.com
<p>This is a regression of <a href="https://pulp.plan.io/issues/6471" class="external">https://pulp.plan.io/issues/6471</a></p>
<p>We are trying to sync the following docker images from satellite server and we got the error while doing sync
1.openshift3/mysql-apb
2.openshift3/mediawiki-apb
3.openshift3/mariadb-apb
4.openshift3/metrics-hawkular-metrics</p>
<p>Getting the below error, when syncing the repository from <a href="http://registry.redhat.io/https://registry.redhat.io" class="external">http://registry.redhat.io/https://registry.redhat.io</a></p>
<pre><code>
Error:
DKR1020: Image download(s) from http://registry.redhat.io/v2/openshift3/mysql-apb/blobs/sha256:1e3f598e03f841ddc4933fafb143d44393d4ce0517604c5cb2367024975e871c failed. Sync task has failed to prevent a corrupted repository.
DKR1020: Image download(s) from https://registry.redhat.io/v2/openshift3/mysql-apb/blobs/sha256:2a81c83bf7ad14e424acbfc7eecaf84aec2b273c25124807d820c4da607644e1 failed. Sync task has failed to prevent a corrupted repository.
Stacktrace:
Apr 1 09:45:10 satellite pulp: nectar.downloaders.threaded:ERROR: (22861-60960) (104, 'Connection reset by peer')
Apr 1 09:45:10 satellite pulp: nectar.downloaders.threaded:ERROR: (22861-60960) Traceback (most recent call last):
Apr 1 09:45:10 satellite pulp: nectar.downloaders.threaded:ERROR: (22861-60960) File "/usr/lib/python2.7/site-packages/nectar/downloaders/threaded.py", line 292, in _fetch
Apr 1 09:45:10 satellite pulp: nectar.downloaders.threaded:ERROR: (22861-60960) for chunk in chunks:
Apr 1 09:45:10 satellite pulp: nectar.downloaders.threaded:ERROR: (22861-60960) File "/usr/lib/python2.7/site-packages/requests/models.py", line 656, in generate
Apr 1 09:45:10 satellite pulp: nectar.downloaders.threaded:ERROR: (22861-60960) for chunk in self.raw.stream(chunk_size, decode_content=True):
Apr 1 09:45:10 satellite pulp: nectar.downloaders.threaded:ERROR: (22861-60960) File "/usr/lib/python2.7/site-packages/requests/packages/urllib3/response.py", line 273, in stream
Apr 1 09:45:10 satellite pulp: nectar.downloaders.threaded:ERROR: (22861-60960) data = self.read(amt=amt, decode_content=decode_content)
Apr 1 09:45:10 satellite pulp: nectar.downloaders.threaded:ERROR: (22861-60960) File "/usr/lib/python2.7/site-packages/requests/packages/urllib3/response.py", line 203, in read
Apr 1 09:45:10 satellite pulp: nectar.downloaders.threaded:ERROR: (22861-60960) data = self._fp.read(amt)
Apr 1 09:45:10 satellite pulp: nectar.downloaders.threaded:ERROR: (22861-60960) File "/usr/lib64/python2.7/httplib.py", line 611, in read
Apr 1 09:45:10 satellite pulp: nectar.downloaders.threaded:ERROR: (22861-60960) s = self.fp.read(amt)
Apr 1 09:45:10 satellite pulp: nectar.downloaders.threaded:ERROR: (22861-60960) File "/usr/lib64/python2.7/socket.py", line 380, in read
Apr 1 09:45:10 satellite pulp: nectar.downloaders.threaded:ERROR: (22861-60960) data = self._sock.recv(left)
Apr 1 09:45:10 satellite pulp: nectar.downloaders.threaded:ERROR: (22861-60960) File "/usr/lib/python2.7/site-packages/requests/packages/urllib3/contrib/pyopenssl.py", line 188, in recv
Apr 1 09:45:10 satellite pulp: nectar.downloaders.threaded:ERROR: (22861-60960) data = self.connection.recv(*args, **kwargs)
Apr 1 09:45:10 satellite pulp: nectar.downloaders.threaded:ERROR: (22861-60960) SysCallError: (104, 'Connection reset by peer')
The workaround is to limit the tags to sync but it is not feasible for some users because they will have to manually update the tags to sync when the upstream repo is updated
</code></pre> RPM Support - Issue #7849 (CLOSED - CURRENTRELEASE): 2.21.4 mkdir fix broke pulp_rpm client codehttps://pulp.plan.io/issues/78492020-11-18T14:47:18Zggainey
<p>In fixing the plethora of mkdirs in Pulp2, we inadvertently made it impossible to use pulp.common.Bundle or pulp.common.Lock unless you have pulp-server installed. We addressed this in pulp with <a class="issue tracker-1 status-11 priority-8 priority-highest closed" title="Issue: 2.21.4 mkdir fix broke client code (CLOSED - CURRENTRELEASE)" href="https://pulp.plan.io/issues/7803">#7803</a>, but missed an instance of the problem in pulp_rpm.</p>
<p>See thread at</p>
<p><a href="https://www.redhat.com/archives/pulp-list/2020-November/msg00037.html" class="external">https://www.redhat.com/archives/pulp-list/2020-November/msg00037.html</a></p> Pulp - Issue #7803 (CLOSED - CURRENTRELEASE): 2.21.4 mkdir fix broke client codehttps://pulp.plan.io/issues/78032020-11-05T20:13:23Zggainey
<p>In fixing the plethora of mkdirs in Pulp2, we inadvertently made it impossible to use pulp.common.Bundle or pulp.common.Lock unless you have pulp-server installed.</p>
<p>See the thread at</p>
<p><a href="https://www.redhat.com/archives/pulp-list/2020-November/msg00008.html" class="external">https://www.redhat.com/archives/pulp-list/2020-November/msg00008.html</a></p>
<p>for details.</p> Pulp - Issue #7726 (CLOSED - CURRENTRELEASE): Pulp2 sets 644 on the files which makes it impossib...https://pulp.plan.io/issues/77262020-10-20T17:59:39Zipanova@redhat.comipanova@redhat.com
<p>These are the current permissions on the files in pulp2</p>
<pre><code>ll /var/lib/pulp/content/units/rpm/ff/9be87993b8e77a5d71ecd04cbbaa7a0386d01a068e3365e05eba20836ecee9/
total 4
-rw-r--r--. 1 apache pulp 1869 Oct 20 16:53 whale-0.2-1.noarch.rpm
</code></pre>
<p>Pulp group can only read the file, however if you want to create a hard link you need to have write permission on the file.
Pulp tries to create a hard link and fails.
This blocks migration.</p> Debian Support - Issue #7674 (CLOSED - CURRENTRELEASE): Fix gnupg metadata verificationhttps://pulp.plan.io/issues/76742020-10-08T12:26:21Zquba42
<p>It looks like a newer version of python2-gnupg now expects the gnupg
home folder to exist before any keys are imported (whereas the older
version presumably just created it if it was not there already).</p> RPM Support - Issue #7660 (CLOSED - CURRENTRELEASE): pulp fails downloading Amazon Linux repositoryhttps://pulp.plan.io/issues/76602020-10-06T21:48:11Zvchepkov
<p>pulp 2.21.3 fails to download packages from Amazon Linux repository. the problem is metadata of Amazon repository, more specifically, time attribute of the rpm package :</p>
<time></time>
<p>importers/yum/repomd/primary.py on line 135 expect value to be integer:</p>
<p>package_info['time'] = int(time_element.attrib['file'])</p>
<p>changing this line to</p>
<p>package_info['time'] = int(time_element.attrib['file'].splt('.')[0])</p>
<p>fixed issue for me</p>
<p>This is stack from failure</p>
<p><a href="https://gist.github.com/vchepkov/1d12035982b46ddd15c8714779eeaac5" class="external">https://gist.github.com/vchepkov/1d12035982b46ddd15c8714779eeaac5</a></p> Docker Support - Issue #7654 (CLOSED - CURRENTRELEASE): Pulp2 overrides permissions set by pulp3https://pulp.plan.io/issues/76542020-10-05T17:24:03Zggainey
<p>Imagine you have pulp2 and some data( in this case i had only ISO content), then pulp3 gets installed.
Write permission for the pulp group is granted and setgid is set [0] Issue comes when new content gets synced into pulp2( in this case I synced an rpm repo) .Pulp2 overrides permissions, this makes is impossible to create a hardlink</p>
<pre><code>$ ll /var/lib/pulp/content/units/
total 12
drwxrwsr-x. 173 apache pulp 4096 Sep 2 08:34 iso <------------------ existing content by the time pulp3 installed
drwxr-sr-x. 12 apache pulp 106 Sep 2 08:35 modulemd <---------------------- new content after pulp3 installed
drwxr-sr-x. 5 apache pulp 36 Sep 2 08:35 modulemd_defaults
drwxr-sr-x. 35 apache pulp 4096 Sep 2 08:35 rpm
(pulp) [vagrant@pulp2-nightly-pulp3-source-centos7 ~
$ ll /var/lib/pulp/content/units/modulemd
total 0
drwxr-sr-x. 2 apache pulp 76 Sep 2 08:35 00
drwxr-sr-x. 2 apache pulp 76 Sep 2 08:35 04
drwxr-sr-x. 2 apache pulp 76 Sep 2 08:35 1b
drwxr-sr-x. 2 apache pulp 76 Sep 2 08:35 41
drwxr-sr-x. 2 apache pulp 76 Sep 2 08:35 66
drwxr-sr-x. 2 apache pulp 76 Sep 2 08:35 78
drwxr-sr-x. 2 apache pulp 76 Sep 2 08:35 8a
drwxr-sr-x. 2 apache pulp 76 Sep 2 08:35 90
drwxr-sr-x. 2 apache pulp 76 Sep 2 08:35 a8
drwxr-sr-x. 2 apache pulp 76 Sep 2 08:35 ea
Then i synced a new ISO repo.
$ ll /var//lib//pulp/content/units/iso/12
total 0
drwxr-sr-x. 2 apache pulp 19 Sep 2 08:33 3f7c65dc3598a59bbb867425c4e52cc54ecb66ff0f6db4656d349799b96594
(pulp) [vagrant@pulp2-nightly-pulp3-source-centos7 ~]$ ll /var//lib//pulp/content/units/iso/12/3f7c65dc3598a59bbb867425c4e52cc54ecb66ff0f6db4656d349799b96594/
</code></pre>
<p>All the content that appears after pulp3 is installed, does not have write permission for the pulp group. This makes it impossible to create hard link during the migration <a href="https://pulp.plan.io/issues/7244" class="external">https://pulp.plan.io/issues/7244</a></p>
<p>[0] <a href="https://github.com/pulp/pulp_installer/blob/master/roles/pulp_common/tasks/install.yml#L107-L133" class="external">https://github.com/pulp/pulp_installer/blob/master/roles/pulp_common/tasks/install.yml#L107-L133</a></p> RPM Support - Issue #7653 (CLOSED - CURRENTRELEASE): Pulp2 overrides permissions set by pulp3https://pulp.plan.io/issues/76532020-10-05T17:17:58Zggainey
<p>Imagine you have pulp2 and some data( in this case i had only ISO content), then pulp3 gets installed.
Write permission for the pulp group is granted and setgid is set [0] Issue comes when new content gets synced into pulp2( in this case I synced an rpm repo) .Pulp2 overrides permissions, this makes is impossible to create a hardlink</p>
<pre><code>$ ll /var/lib/pulp/content/units/
total 12
drwxrwsr-x. 173 apache pulp 4096 Sep 2 08:34 iso <------------------ existing content by the time pulp3 installed
drwxr-sr-x. 12 apache pulp 106 Sep 2 08:35 modulemd <---------------------- new content after pulp3 installed
drwxr-sr-x. 5 apache pulp 36 Sep 2 08:35 modulemd_defaults
drwxr-sr-x. 35 apache pulp 4096 Sep 2 08:35 rpm
(pulp) [vagrant@pulp2-nightly-pulp3-source-centos7 ~
$ ll /var/lib/pulp/content/units/modulemd
total 0
drwxr-sr-x. 2 apache pulp 76 Sep 2 08:35 00
drwxr-sr-x. 2 apache pulp 76 Sep 2 08:35 04
drwxr-sr-x. 2 apache pulp 76 Sep 2 08:35 1b
drwxr-sr-x. 2 apache pulp 76 Sep 2 08:35 41
drwxr-sr-x. 2 apache pulp 76 Sep 2 08:35 66
drwxr-sr-x. 2 apache pulp 76 Sep 2 08:35 78
drwxr-sr-x. 2 apache pulp 76 Sep 2 08:35 8a
drwxr-sr-x. 2 apache pulp 76 Sep 2 08:35 90
drwxr-sr-x. 2 apache pulp 76 Sep 2 08:35 a8
drwxr-sr-x. 2 apache pulp 76 Sep 2 08:35 ea
Then i synced a new ISO repo.
$ ll /var//lib//pulp/content/units/iso/12
total 0
drwxr-sr-x. 2 apache pulp 19 Sep 2 08:33 3f7c65dc3598a59bbb867425c4e52cc54ecb66ff0f6db4656d349799b96594
(pulp) [vagrant@pulp2-nightly-pulp3-source-centos7 ~]$ ll /var//lib//pulp/content/units/iso/12/3f7c65dc3598a59bbb867425c4e52cc54ecb66ff0f6db4656d349799b96594/
</code></pre>
<p>All the content that appears after pulp3 is installed, does not have write permission for the pulp group. This makes it impossible to create hard link during the migration <a href="https://pulp.plan.io/issues/7244" class="external">https://pulp.plan.io/issues/7244</a></p>
<p>[0] <a href="https://github.com/pulp/pulp_installer/blob/master/roles/pulp_common/tasks/install.yml#L107-L133" class="external">https://github.com/pulp/pulp_installer/blob/master/roles/pulp_common/tasks/install.yml#L107-L133</a></p> Pulp - Issue #7526 (CLOSED - CURRENTRELEASE): Publish is operational when the only change in conf...https://pulp.plan.io/issues/75262020-09-18T06:47:53Zttereshcttereshc@redhat.com
<p>To reproduce:</p>
<ul>
<li>Publish a repo override_config {"force_full":true}</li>
<li>Then publish without override config or with {"force_full":false}.</li>
</ul>
<p>The second publish will be operational.</p> RPM Support - Refactor #7505 (CLOSED - CURRENTRELEASE): Drop --local-sqlite for createrepo_c to a...https://pulp.plan.io/issues/75052020-09-15T10:31:34Zmhaluza
<p>Commit ca24ae2 referenced via <a href="https://pulp.plan.io/issues/1157" class="external">https://pulp.plan.io/issues/1157</a> as internal need for the former RCM team introduced --local-sqlite parameter for createrepo_c to speed up publish process in a scenario where pulp filesystems were located on NFS. This need is no longer valid.</p>
<p>Currently, the --local-sqlite causes createrepo_c to write to TMPDIR instead of its usual output directory, which causes huge sqlite files to be left under /tmp after cancelled or failed Pulp tasks. /tmp is oftentimes fairly small and this may cause the filesystem to fill up quickly. Pulp already has the concept of creating a temporary working directory for each task under /var/lib/pulp/working and cleaning it up at the end. Usage of this working directory should be preferred.</p>
<p>Suggested change: <a href="https://github.com/pulp/pulp_rpm/pull/1833" class="external">https://github.com/pulp/pulp_rpm/pull/1833</a></p> RPM Support - Issue #7480 (CLOSED - CURRENTRELEASE): Pulp worker can consume high memory when pub...https://pulp.plan.io/issues/74802020-09-09T13:55:22Zhyu
<p>Clone from bugzilla 1876782</p>
<p>Description of problem:
When publishing a repository with large metadata file (such as the others.xml.gz file in rhel-7-server-rpms). The Pulp worker can consumes more than 3GB of RAM for a few minutes. After that, the memory is freed to normally usage which is ok.</p>
<p>When calculating the open-size of a metadata, Pulp opens the gzip file which loads the whole gzip file into the memory.</p>
<a name="pluginsdistributorsyummetadatarepomdpy"></a>
<h2 >plugins/distributors/yum/metadata/repomd.py<a href="#pluginsdistributorsyummetadatarepomdpy" class="wiki-anchor">¶</a></h2>
<pre><code> if file_path.endswith('.gz'):
open_size_element = ElementTree.SubElement(data_element, 'open-size')
open_checksum_attributes = {'type': self.checksum_type}
open_checksum_element = ElementTree.SubElement(data_element, 'open-checksum',
open_checksum_attributes)
try:
file_handle = gzip.open(file_path, 'r') <============= Here
except:
# cannot have an else clause to the try without an except clause
raise
else:
try:
content = file_handle.read()
open_size_element.text = str(len(content))
open_checksum_element.text = self.checksum_constructor(content).hexdigest()
finally:
file_handle.close()
</code></pre>
<hr>
<p>This is not quite an issue if user is syncing only a few repos. In the case of Satellite, user may sync large repositories at the same time, such as the Optimized Capsule sync. If one Capsule has 8 workers and each worker consumes 4GB+ of memory then the Capsule will run out of memory.</p>
<p>Steps to Reproduce:</p>
<ol>
<li>Set Pulp to use only 1 worker so that we can monitor the progress easily.</li>
<li>Force full publish a rhel-7-server-rpms repository.</li>
<li>Use the following command to monitor the memory usage.</li>
</ol>
<p>watch 'ps -aux | grep reserved_resource_worker-0'</p>
<ol start="4">
<li>The high memory consumption happens when Pulp finalizing the others.xml.gz file. You can use the following command to monitor the pulp working directory.</li>
</ol>
<p>cd /var/cache/pulp/reserved_resource_worker-0@//
watch 'ls -alrth'</p> Pulp - Issue #7445 (CLOSED - CURRENTRELEASE): Pulp2 overrides permissions set by pulp3https://pulp.plan.io/issues/74452020-09-02T10:31:57Zipanova@redhat.comipanova@redhat.com
<p>Imagine you have pulp2 and some data( in this case i had only ISO content), then pulp3 gets installed.
Write permission for the pulp group is granted and setgid is set [0] Issue comes when new content gets synced into pulp2( in this case I synced an rpm repo) .Pulp2 overrides permissions, this makes is impossible to create a hardlink</p>
<pre><code>$ ll /var/lib/pulp/content/units/
total 12
drwxrwsr-x. 173 apache pulp 4096 Sep 2 08:34 iso <------------------ existing content by the time pulp3 installed
drwxr-sr-x. 12 apache pulp 106 Sep 2 08:35 modulemd <---------------------- new content after pulp3 installed
drwxr-sr-x. 5 apache pulp 36 Sep 2 08:35 modulemd_defaults
drwxr-sr-x. 35 apache pulp 4096 Sep 2 08:35 rpm
(pulp) [vagrant@pulp2-nightly-pulp3-source-centos7 ~
$ ll /var/lib/pulp/content/units/modulemd
total 0
drwxr-sr-x. 2 apache pulp 76 Sep 2 08:35 00
drwxr-sr-x. 2 apache pulp 76 Sep 2 08:35 04
drwxr-sr-x. 2 apache pulp 76 Sep 2 08:35 1b
drwxr-sr-x. 2 apache pulp 76 Sep 2 08:35 41
drwxr-sr-x. 2 apache pulp 76 Sep 2 08:35 66
drwxr-sr-x. 2 apache pulp 76 Sep 2 08:35 78
drwxr-sr-x. 2 apache pulp 76 Sep 2 08:35 8a
drwxr-sr-x. 2 apache pulp 76 Sep 2 08:35 90
drwxr-sr-x. 2 apache pulp 76 Sep 2 08:35 a8
drwxr-sr-x. 2 apache pulp 76 Sep 2 08:35 ea
Then i synced a new ISO repo.
$ ll /var//lib//pulp/content/units/iso/12
total 0
drwxr-sr-x. 2 apache pulp 19 Sep 2 08:33 3f7c65dc3598a59bbb867425c4e52cc54ecb66ff0f6db4656d349799b96594
(pulp) [vagrant@pulp2-nightly-pulp3-source-centos7 ~]$ ll /var//lib//pulp/content/units/iso/12/3f7c65dc3598a59bbb867425c4e52cc54ecb66ff0f6db4656d349799b96594/
</code></pre>
<p>All the content that appears after pulp3 is installed, does not have write permission for the pulp group. This makes it impossible to create hard link during the migration <a href="https://pulp.plan.io/issues/7244" class="external">https://pulp.plan.io/issues/7244</a></p>
<p>[0] <a href="https://github.com/pulp/pulp_installer/blob/master/roles/pulp_common/tasks/install.yml#L107-L133" class="external">https://github.com/pulp/pulp_installer/blob/master/roles/pulp_common/tasks/install.yml#L107-L133</a></p> Docker Support - Issue #7214 (CLOSED - CURRENTRELEASE): Improve error message for registry errorshttps://pulp.plan.io/issues/72142020-07-27T06:58:16Zlgallovi
<p>The current error message setup is misleading for the end users, as it strips away the status code, error type, and url. The users are (for example) left with 'IOError('Internal server error')' which makes then unable to determine which service is experiencing the issues. The error message should be extended to include more information.</p> Pulp - Issue #7185 (CLOSED - CURRENTRELEASE): force_full rsync publish is done unnecessarily in s...https://pulp.plan.io/issues/71852020-07-22T03:03:30Zyuzhengyuzheng@redhat.com
<p>A full rsync publish is done when some criteria are met (defined in <a href="https://github.com/pulp/pulp/blob/2-master/server/pulp/plugins/rsync/publish.py#L373" class="external">https://github.com/pulp/pulp/blob/2-master/server/pulp/plugins/rsync/publish.py#L373</a>). Some of the criteria don't need a full rsync publish to make the right content published to rsync distributor:</p>
<ul>
<li>When there's units removal since last rsync publish</li>
<li>When there's predistributor publish failure since last rsync publish</li>
</ul>
<p>Since it takes longer time to do full publish, especially for big repos containing lots of units, unnecessary full publish should be avoided by removing above criteria.</p> Docker Support - Issue #6471 (CLOSED - CURRENTRELEASE): Unable to sync large openshift docker reposhttps://pulp.plan.io/issues/64712020-04-09T11:52:22Zhyu
<p>We are trying to sync the following docker images from satellite server and we got the error while doing sync
1.openshift3/mysql-apb
2.openshift3/mediawiki-apb
3.openshift3/mariadb-apb
4.openshift3/metrics-hawkular-metrics</p>
<p>Getting the below error, when syncing the repository from <a href="http://registry.redhat.io/https://registry.redhat.io" class="external">http://registry.redhat.io/https://registry.redhat.io</a></p>
<pre><code>
Error:
DKR1020: Image download(s) from http://registry.redhat.io/v2/openshift3/mysql-apb/blobs/sha256:1e3f598e03f841ddc4933fafb143d44393d4ce0517604c5cb2367024975e871c failed. Sync task has failed to prevent a corrupted repository.
DKR1020: Image download(s) from https://registry.redhat.io/v2/openshift3/mysql-apb/blobs/sha256:2a81c83bf7ad14e424acbfc7eecaf84aec2b273c25124807d820c4da607644e1 failed. Sync task has failed to prevent a corrupted repository.
Stacktrace:
Apr 1 09:45:10 satellite pulp: nectar.downloaders.threaded:ERROR: (22861-60960) (104, 'Connection reset by peer')
Apr 1 09:45:10 satellite pulp: nectar.downloaders.threaded:ERROR: (22861-60960) Traceback (most recent call last):
Apr 1 09:45:10 satellite pulp: nectar.downloaders.threaded:ERROR: (22861-60960) File "/usr/lib/python2.7/site-packages/nectar/downloaders/threaded.py", line 292, in _fetch
Apr 1 09:45:10 satellite pulp: nectar.downloaders.threaded:ERROR: (22861-60960) for chunk in chunks:
Apr 1 09:45:10 satellite pulp: nectar.downloaders.threaded:ERROR: (22861-60960) File "/usr/lib/python2.7/site-packages/requests/models.py", line 656, in generate
Apr 1 09:45:10 satellite pulp: nectar.downloaders.threaded:ERROR: (22861-60960) for chunk in self.raw.stream(chunk_size, decode_content=True):
Apr 1 09:45:10 satellite pulp: nectar.downloaders.threaded:ERROR: (22861-60960) File "/usr/lib/python2.7/site-packages/requests/packages/urllib3/response.py", line 273, in stream
Apr 1 09:45:10 satellite pulp: nectar.downloaders.threaded:ERROR: (22861-60960) data = self.read(amt=amt, decode_content=decode_content)
Apr 1 09:45:10 satellite pulp: nectar.downloaders.threaded:ERROR: (22861-60960) File "/usr/lib/python2.7/site-packages/requests/packages/urllib3/response.py", line 203, in read
Apr 1 09:45:10 satellite pulp: nectar.downloaders.threaded:ERROR: (22861-60960) data = self._fp.read(amt)
Apr 1 09:45:10 satellite pulp: nectar.downloaders.threaded:ERROR: (22861-60960) File "/usr/lib64/python2.7/httplib.py", line 611, in read
Apr 1 09:45:10 satellite pulp: nectar.downloaders.threaded:ERROR: (22861-60960) s = self.fp.read(amt)
Apr 1 09:45:10 satellite pulp: nectar.downloaders.threaded:ERROR: (22861-60960) File "/usr/lib64/python2.7/socket.py", line 380, in read
Apr 1 09:45:10 satellite pulp: nectar.downloaders.threaded:ERROR: (22861-60960) data = self._sock.recv(left)
Apr 1 09:45:10 satellite pulp: nectar.downloaders.threaded:ERROR: (22861-60960) File "/usr/lib/python2.7/site-packages/requests/packages/urllib3/contrib/pyopenssl.py", line 188, in recv
Apr 1 09:45:10 satellite pulp: nectar.downloaders.threaded:ERROR: (22861-60960) data = self.connection.recv(*args, **kwargs)
Apr 1 09:45:10 satellite pulp: nectar.downloaders.threaded:ERROR: (22861-60960) SysCallError: (104, 'Connection reset by peer')
The workaround is to limit the tags to sync but it is not feasible for some users because they will have to manually update the tags to sync when the upstream repo is updated
</code></pre>