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.

We need to create a sub package for ostree. 

That sub package needs to include
1) a dep on pulp-ostree-plugins
2) include lib/katello/repository_types/ostree.rb
3) Fix katello spec to exclude lib/katello/repository_types/ostree.rb

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

Upstream bug assigned to paji

Fixed in -> https://github.com/Katello/katello-packaging/pull/168

Verified with sat6.2 beta snap6

following packages have been installed with ostree and its plugin:

[root@cloud-qe-15 foreman-proxy]# rpm -qa | grep ostree
python-pulp-ostree-common-1.1.0.2-1.el7sat.noarch
tfm-rubygem-katello_ostree-3.0.0.12-1.el7sat.noarch
ostree-2016.1-2.atomic.el7.x86_64
pulp-ostree-plugins-1.1.0.2-1.el7sat.noarch

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/RHBA-2016:1500