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 867624 - Content Deletion - deleting repos with changeset report success before completion
Summary: Content Deletion - deleting repos with changeset report success before comple...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: API
Version: 6.0.0
Hardware: Unspecified
OS: Linux
medium
medium
Target Milestone: Unspecified
Assignee: Katello Bug Bin
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-10-17 21:07 UTC by Brad Buckingham
Modified: 2014-02-18 14:44 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-02-18 14:44:30 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Brad Buckingham 2012-10-17 21:07:19 UTC
Description of problem:

If a user deletes some repositories (using a deletion changeset) and then attempts to re-promote the repo after being notified that the deletion is complete, they may receive an error during the promotion attempt.  

The issue is that the deletion is reported as 'successful'; however, pulp is continuing to delete the repository.  After the repository is fully deleted from pulp (e.g. wait longer), the user can successfully re-promote the repository.

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

How reproducible:
easy, if the repository is large and user re-promotes right after deletion reports success...

Steps to Reproduce:

basic setup:
============
environment create --org ACME_Corporation --name dev --prior Library
environment create --org ACME_Corporation --name test --prior dev

provider create --org ACME_Corporation --name prov1
product create --org ACME_Corporation --provider prov1 --name prod1
repo create --org ACME_Corporation --product prod1 --name repo1 --url [largerepo]
repo create --org ACME_Corporation --product prod1 --name repo2 --url [largerepo]
repo synchronize --org ACME_Corporation --product prod1 --name repo1
repo synchronize --org ACME_Corporation --product prod1 --name repo2

promote the product (consisting of the 2 large repos - e.g. rhel6):
==================================================================
changeset create --name prod1_to_dev --env dev --org ACME_Corporation
changeset update --add_product prod1 --name prod1_to_dev --org ACME_Corporation --environment dev
changeset apply --env dev --org ACME_Corporation --name prod1_to_dev

delete the 2 repos from dev:
============================
changeset create --name remove_2_repos --env dev --org ACME_Corporation --deletion
changeset update --from_product prod1 --add_repo repo1 --name remove_2_repos --org ACME_Corporation --environment dev
changeset update --from_product prod1 --add_repo repo2 --name remove_2_repos --org ACME_Corporation --environment dev
changeset apply --env dev --org ACME_Corporation --name remove_2_repos

promote the first repo: (promoting same repos as deleted above:)
================================================================
changeset create --name add_repo1 --env dev --org ACME_Corporation
changeset update --from_product prod1 --add_repo repo1 --name add_repo1 --org ACME_Corporation --environment dev
changeset apply --env dev --org ACME_Corporation --name add_repo1
 
Actual results:

The following error observed after the last 'changeset apply':

Changeset [ add_repo1 ] promotion failed: Resources::Pulp::Repository: 409 Conflict "A repository with the id, ACME_Corporation-dev-prod1-repo1, already exists" (POST /pulp/api/repositories/ACME_Corporation-prod1-repo1/clone/)


Expected results:

The expectation is that when the apply of 'remove_2_repos' reports successful completion, the user is able to successfully create/update/apply the add_repo1 changeset.


Additional info:

Comment 2 Justin Sherrill 2013-01-22 21:16:32 UTC
FYI pulpv2 provides tasks for repo deletion that we can wait on.  Integrating that into orchestration might be tricky, but we can fix it in pulpv2 branch.

Comment 3 Bryan Kearney 2014-02-18 14:44:30 UTC
This bug is against katello-cli which we are no longer supporting. Closing.


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