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.

Since the ostree repos are not available on the cdn yet, enabling them in the OSTree tab of the Red Hat Repositories page will (properly) show an error. However, some part of them has been partially created in pulp which causes error when user attempts to refresh manifest.

In glue/pulp/repo.rb the lazy_accessor :importers will error on manifest refresh.

The OSTree repo will show up as enabled in the UI but errors when trying to disable it.

My suggestion would be to make sure that the initial enable is fully rolled back on an error.

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

I consider this a development environment issue and not a sat production issue, because Satellite customers will not get into this state. Basically without the --katello-enable-ostree=true customers will not be able to see OSTree repos that can be enabled.
Its not the case in the dev environment and hence Tom hit that. Going to remove the flags out and mark it a non blocker. This should be addressed upstream only.