Bug 1134100

Description of problem:
When a user has capsule(s) attached to an instance, and attempts to publish/promote content, said content is synced twice to capsule -- once during the initial publish process and then again afterwards.

Version-Release number of selected component (if applicable):
Satellite-6.0.4-RHEL-6-20140823.0

How reproducible:


Steps to Reproduce:
1.  Attach a capsule to your sat
2.  Create a content view and attempt to publish/promote it.
3.  Note dynflow tasks and/or possibly just talk w/ a knowledgeable developer who understands what the heck is going on (jsherrill!)

Actual results:
Apparently, this is the situation.

* Previously, as part of a publish, new content was immediately pushed out to capsules as part of that publish
* There was discussion to break this into two tasks - do initial pub/promote to library and spawn a second task to sync.
* I am not sure whether a real decision was made on the behavior in the bullet above, but whatever the case, we're apparently still doing a sync during the initial publish -- followed by a second sync immediately after.

Expected results:

Apparently there was a lot of discussion between dev on how to handle the sync, whether to keep it as one big monolithic function (promote/publish/capsule sync) or break it out (promote/pub THEN content sync).  As an end user I think the second behavior is more palatable because otherwise user is sitting there on a publish that takes ages and user has no idea why.  Regardless, we shouldn't be syncing twice, independent of workflow decision.


Additional info: