Bug 963408

Summary: rpm repos can be synced with iso sync run
Product: [Retired] Pulp Reporter: Preethi Thomas <pthomas>
Component: iso-supportAssignee: pulp-bugs
Status: CLOSED UPSTREAM QA Contact: Preethi Thomas <pthomas>
Severity: unspecified Docs Contact:
Priority: low    
Version: MasterCC: cduryee, mhrivnak, mmccune, skarmark
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-28 21:55:04 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Preethi Thomas 2013-05-15 18:21:54 UTC
Description of problem:

If you run iso sync run on a rpm repo. The progress is not reported but if you see the log, you see the sync is running.

Version-Release number of selected component (if applicable):
[root@ibm-x3550m3-07 ~]# rpm -q pulp-server
pulp-server-2.2.0-0.5.alpha.el6.noarch


How reproducible:


Steps to Reproduce:
1. Create a rpm and run rpm repo sync
2. Run iso repo sync run on the above repo
3. tail the pulp.log
  
Actual results:

[root@ibm-x3550m3-07 ~]# pulp-admin iso repo sync run --repo-id myepel-repo
+----------------------------------------------------------------------+
                 Synchronizing Repository [myepel-repo]
+----------------------------------------------------------------------+

This command may be exited by pressing ctrl+c without affecting the actual
operation on the server.

Expected results:


Additional info:

Comment 3 Chris Duryee 2014-11-07 22:17:11 UTC
*** Bug 997186 has been marked as a duplicate of this bug. ***

Comment 4 Chris Duryee 2014-11-07 22:17:58 UTC
bz is still outstanding as of 2.5.0

Comment 5 Brian Bouterse 2015-02-28 21:55:04 UTC
Moved to https://pulp.plan.io/issues/350