Bug 1196390 - Pulp-admin fails to publish rpm repo with serve-http and serve-https set false
Summary: Pulp-admin fails to publish rpm repo with serve-http and serve-https set false
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Pulp
Classification: Retired
Component: rpm-support
Version: 2.5
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: pulp-bugs
QA Contact: pulp-qe-list
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-02-25 21:44 UTC by Marc Chadwick
Modified: 2015-02-28 23:26 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-02-28 23:26:10 UTC


Attachments (Terms of Use)
Log output (2.27 KB, text/plain)
2015-02-25 21:44 UTC, Marc Chadwick
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Pulp Redmine 717 0 None None None Never

Description Marc Chadwick 2015-02-25 21:44:17 UTC
Created attachment 995349 [details]
Log output

Description of problem:

If an rpm repository has both serve-http and serve-https set to false, and if at least one rpm in its contents, publish fails. Pulp-admin displays the following error:

Task Failed

coercing to Unicode: need string or buffer, NoneType found

I am attaching a text file with the contents of ~/.pulp/server_calls.log.

The publish succeeds if there is no content in the repo. 

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

pulp-admin-client-2.5.3-1.el6.noarch

How reproducible:

100%

Steps to Reproduce:
1. pulp-admin rpm repo create --repo-id foo --serve-http false --serve-https false
2. Upload or copy an RPM into this repo
3. pulp-admin rpm repo publish run --repo-id foo

Actual results:
Task Failed

coercing to Unicode: need string or buffer, NoneType found

Expected results:
Publish should succeed and remove any previously published data.

Additional info:
Extra thanks to bcourt on IRC who helped track this down and asked that I open this bug

Comment 1 Barnaby Court 2015-02-25 21:58:42 UTC
This bug specifically kicks in when the incremental publish code is invoked and both serve-http and serve-https is set to false.

Comment 2 Brian Bouterse 2015-02-28 23:26:10 UTC
Moved to https://pulp.plan.io/issues/717


Note You need to log in before you can comment on or make changes to this bug.