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.

Moving this out of 6.1.7 due to capacity issues. Will keep it on the 6.1.z and 6.2 trackers to ensure that it is evaluated for both.

upstram bug is ON_QA, moving to POST.

This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions

There is no actual fix for this bug and no reason it should be in the POST state. Moving this to NEW

Nearly everything changed from 6.1 to 6.2 about how puppet modules get sync'd from a Satellite server to a Capsule. Can this be re-tested?

Brad, can we lower the priority and severity, on the grounds that virtually none of the same behaviors are still in use in 6.2?

I'm closing this since it appears resolved in 6.2. Dhananjay, let us know if you need further assistance with this issue.