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 798339 - If promotion fails, please rollback
Summary: If promotion fails, please rollback
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Management
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: Lukas Zapletal
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-28 16:49 UTC by Og Maciel
Modified: 2014-03-12 22:53 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-03-12 22:53:10 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Og Maciel 2012-02-28 16:49:52 UTC
Description of problem:

If I'm promoting content to an environment for the first time (or even if not the first time for that matter) and something causes this process to fail somewhere along the way, pulp will leave content from this partial promotion in its local filesystem, which to me is not the best thing to do, not to say that it could lead to complications in the future, when the promotion does work eventually. I'd like to see promotions and syncs behave more like a database transaction, where partial successful operations get "rolled back" and only 100% successful operations get "committed" to the system.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

See BZs https://bugzilla.redhat.com/show_bug.cgi?id=798299 and https://bugzilla.redhat.com/show_bug.cgi?id=798301 for more information on how I came to see partial committed content to my system. Since my promotion failed, I should not see content for my custom SystemEngine -> Hourly repository but I did have content as shown here:

/var/lib/pulp/repos/SaoPaulo/Dev1/custom/SystemEngine/Hourly/packages/

Comment 1 Mike McCune 2012-02-29 00:21:44 UTC
ideal but time consuming to implement.  Advocating we fix in V1+

Comment 2 Lukas Zapletal 2014-03-12 10:04:20 UTC
Bug is irrelevant because orchestration is being rewritten.

Comment 3 Bryan Kearney 2014-03-12 22:53:10 UTC
Closing old bugs which are not relevant based on new UI and CLI


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