Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
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