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.

Most RHN Satellite users (Goldman, Bank of America, Dreamworks, AOL, UBS to name
a few) work with a subset of the complete RHEL package set and would prefer to
divide it into smaller chunks rather than have 1200+ packages in the same
channel. What they are asking for is to have RHEL delivered as many channels
rather than one. The thing is they all use a different "core build".

Can we set up rules under the new channel model to allow them to define how a
channel is subdivided and have the resulting channels automatically inherit
appropriate updates/Errata rather than forcing them to clone a channel, remove
packages, and then manually clone the Errata?

This is solved via Satellite 6's Content Views feature.

You have the ability to filter specific packages and errata from within a repository (channel), combine those filtered repositories into a 'Content View' and then combine a series of Content Views into a larger view, known as a Composite Content View to completely customize the content made available to your end systems.