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/