Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 865808 - Pulp id has already been taken
Summary: Pulp id has already been taken
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Management
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: Unspecified
Assignee: Justin Sherrill
QA Contact: Og Maciel
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-10-12 13:40 UTC by Thom Carlin
Modified: 2014-09-18 15:32 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-01-22 16:21:38 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Thom Carlin 2012-10-12 13:40:40 UTC 
Description of problem:

Promotions fail with "Pulp id has already been taken"

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

pulp 1.1.12-1.el6cf

How reproducible:

Evertime once it fails

Steps to Reproduce:
1. Unclear, initial promotion failed, subsequent result in this error
2.
3.
  
Actual results:

"Pulp id has already been taken"

Expected results:

Changset properly promoted

Additional info:

Reported by user:
> pending?falsetask_typefinish_time2012-10-11
04:16:38stateerroruser_id0start_timeresulterrorsE11000 duplicate key
error index: pulp_database.packages.$_id_ dup key: { :
"d8a8a4a6-784c-40a2-95aa-a9fd7d2d80ab" }Traceback (most recent call
last): File
"/usr/lib/python2.6/site-packages/pulp/server/tasking/task.py", line
418, in run result = self.callable(*self.args, **self.kwargs) File
"/usr/lib/python2.6/site-packages/pulp/server/api/repo_sync.py", line
146, in _clone _sync(clone_id, progress_callback=progress_callback,
synchronizer=synchronizer) File
"/usr/lib/python2.6/site-packages/pulp/server/api/repo_sync.py", line
283, in _sync progress_callback, synchronizer, max_speed, threads) File
"/usr/lib/python2.6/site-packages/pulp/server/api/repo_sync.py", line
373, in fetch_content added_packages =
synchronizer.process_packages_from_source(repo_dir, repo_id, skip_dict,
progress_callback) File ...
Comment 4 Mike McCune 2012-10-22 16:19:28 UTC 
moving to 2.0 since we aren't reliably reproducing this.  if it starts happening more often we can escalate
Comment 5 Justin Sherrill 2013-01-22 16:12:15 UTC 
Is this able to be reproduced?  I am not able to reproduce locally and without a reproducer or at least a katello-debug, there isn't much more we can do.
Comment 6 Thom Carlin 2013-01-22 16:21:38 UTC 
Agreed, closed.  We can reopen it if it reoccurs on 1.1.x
Note You need to log in before you can comment on or make changes to this bug.