Bug 798339 - If promotion fails, please rollback
If promotion fails, please rollback
Product: Red Hat Satellite 6
Classification: Red Hat
Component: Content Management (Show other bugs)
Unspecified Unspecified
unspecified Severity medium (vote)
: Unspecified
: --
Assigned To: Lukas Zapletal
Katello QA List
: Triaged
Depends On:
  Show dependency treegraph
Reported: 2012-02-28 11:49 EST by Og Maciel
Modified: 2014-03-12 18:53 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2014-03-12 18:53:10 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Og Maciel 2012-02-28 11:49:52 EST
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:
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:

Comment 1 Mike McCune 2012-02-28 19:21:44 EST
ideal but time consuming to implement.  Advocating we fix in V1+
Comment 2 Lukas Zapletal 2014-03-12 06:04:20 EDT
Bug is irrelevant because orchestration is being rewritten.
Comment 3 Bryan Kearney 2014-03-12 18:53:10 EDT
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.