Description of problem: Publishing a repo throws error on first run after a package has been deleted from it. Rerun runs fine.


Version-Release number of selected component (if applicable):2.5.1


How reproducible:


Steps to Reproduce:
1. remove package from repo [/usr/bin/pulp-admin -u admin -p admin rpm repo remove rpm --repo-id pulp-2.5.1 --str-eq='filename=nmr-pulp-2.5.1-1.x86_64.rpm']
2. clear orphans: [/usr/bin/pulp-admin -u admin -p admin  orphan remove --all]
3. publish repo: [/usr/bin/pulp-admin -u admin rpm repo publish run --repo-id pulp-2.5.1]

Actual results:
+----------------------------------------------------------------------+
                   Publishing Repository [pulp-2.5.1]
+----------------------------------------------------------------------+

This command may be exited via ctrl+c without affecting the request.


Initializing repo metadata
[-]
... completed

Publishing Distribution files
[-]
... completed

Publishing RPMs
[===                                               ] 6%
6 of 89 items
... failed
Incorrect length of data produced


Task Failed

Incorrect length of data produced

-----------------------------------------------------------------------------

Expected results:
+----------------------------------------------------------------------+
                   Publishing Repository [pulp-2.5.1]
+----------------------------------------------------------------------+

This command may be exited via ctrl+c without affecting the request.


Copying files
[-]
... completed

Initializing repo metadata
[-]
... completed

Publishing Distribution files
[-]
... completed

Publishing RPMs
[-]
... completed

Publishing Delta RPMs
... skipped

Publishing Errata
[-]
... completed

Publishing Comps file
[==================================================] 100%
7 of 7 items
... completed

Publishing Metadata.
[-]
... completed

Closing repo metadata
[-]
... completed

Generating sqlite files
... skipped

Publishing files to web
[-]
... completed

Writing Listings File
[-]
... completed


Task Succeeded


Additional info:
not sure if delay has got anything to do here, but we did run publish after 10s but got the same error.