[Pulp-list] Content Upload Fails for ISOs

Brian Bouterse bbouters at redhat.com
Fri Sep 2 20:56:58 UTC 2016

We resolved this on IRC, but for others. The ISO upload does require the 
size specified where as other content types don't.

One common thing I do when integrating with the pulp REST API is to try 
the action I want with pulp-admin first. If it works, then I run it with:

pulp-admin -vv <rest of command>

This shous every call pulp-admin makes and every response. Of course 
having a consistent API would help. Did I mention we're working on Pulp 3?

All the best,

On 09/02/2016 08:44 AM, Eric Helms wrote:
> I am attempting to upload a large file to the ISO importer via the
> content upload workflow (create request, upload chunks and then import).
> When I do this I am seeing an error in the Pulp logs:
> summary: Downloading <None> failed validation. The manifest specified
> that the
>       file should be None bytes, but the downloaded file is 103248 bytes.
> Doing some digging, it appears the ISO importer does a validation step
> [1] where it computes and compares sizes. However, the 'self.size' does
> not get set during content upload. Am I reading that correct? Is there a
> way around this? Or a hack/patch?
> Thanks,
> Eric
> [1] https://github.com/pulp/pulp_rpm/blob/4678cc697458ec207996bee2d851f72db190c167/plugins/pulp_rpm/plugins/importers/iso/importer.py#L141
> [2] https://github.com/pulp/pulp_rpm/blob/4678cc697458ec207996bee2d851f72db190c167/plugins/pulp_rpm/plugins/db/models.py#L665
> _______________________________________________
> Pulp-list mailing list
> Pulp-list at redhat.com
> https://www.redhat.com/mailman/listinfo/pulp-list

More information about the Pulp-list mailing list