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.

Currently incremental updates with composites are a tad lacking:

a) the systems_bulk_action_controller#available_incremental_updates does not tell you which ones are composites and their components, this needs to be split up
b) the main incremental update api should not accept composite content view versions.  You should have to supply the component to update and specify that you want to propagate to composites

Created from redmine issue http://projects.theforeman.org/issues/9120f

Upstream bug assigned to jsherril

Moving to POST since upstream bug http://projects.theforeman.org/issues/9120f has been closed
-------------
Justin Sherrill
Applied in changeset commit:katello|518ca32c130e0de73587d40744e4ec23b9454a4c.

Verified.

Satellite-6.1.0-RHEL-6-20150317.0

This bug is slated to be released with Satellite 6.1.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2015:1592