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:

Satellite 6 does not currently support delta RPMs.

The purpose of this bugzilla is to add support for delta RPM as a unit.

This means the ability to perform actions such as the following:
- sync yum repositories containing delta RPMs
- upload or delete delta RPMs from a yum repository
- ability to list delta RPMs in repository
- ability to list delta RPMs across a lifecycle environment
- ability to list delta RPMs across the organization the organization
- ability to view information on a delta RPM
- ability to publish delta RPMs in a content view
- ability to promote CV versions containing delta RPMs
- ability to list the delta RPMs within a CV version
- including the count of delta RPMs in repositories, content view version...etc

- Note: the above would not include defining content view filtering specific to delta RPMs
- The assumption would be that all actions would be support via the UI/API/CLI