Description of problem: Sometimes if user tries to publish promote content in a content view immediately after content appears to have finished syncing (as initiated from Content > Sync Status), the user's content does not really get where it needs to go Version-Release number of selected component (if applicable): Satellite-6.0.3-RHEL-6-20140612.1 How reproducible: Steps to Reproduce: 1. Create a content view and have it ready and waiting. 2. Sync RHEL content from Conten > Sync Status and wait for it to finish 3. As soon as UI says it is 'done', add to cv publish and promote. 4. Register system to env/cv and try and pull content and/or 'yum repolist' Actual results: yum repolist tells us rhel-6-server-rpms Red Hat Enterprise Linux 6 Server (RPMs) 0 Content does not properly get published/promoted Expected results: Implement dynflow in the content sync page so that it "plays" better w the rest of the UI. Additional info: [10:20] < jsherrill> the sync status page just needs to be updated for dynflow :( [10:21] < partha> jsherrill: we should dynflow that page
The sync status page is being updated to use dynflow using bug 1122249 . *** This bug has been marked as a duplicate of bug 1122249 ***