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:
SSIA

Version-Release number of selected component (if applicable):
sat 7.0 snap 9 and snap 10, well both of them running on RHEL 8.5


How reproducible:
Always

Steps to Reproduce:
1. run  satellite-installer --foreman-proxy-content-enable-ostree
2. Via UI, Create product
3. New repository

Actual results:
In type field there is no ostree

Expected results:
In the typefield there is ostree. 

Additional info:
I tried to create a repo in CLI hitting the same problem:
Validation failed: Content type is not enabled. must be one of the following: ansible_collection, docker, file, yum

It is possible that another step is required but it's not mentioned in the documentation.
steps were based on documentation:
https://docs.theforeman.org/nightly/Content_Management_Guide/index-satellite.html#con_managing-ostree-content_content-management


I believe this is not a regression as this is introduced as new functionality in foreman demo #104
https://www.youtube.com/watch?v=UWHy7NuR9yA

There seem to be 2 issues here, one is that the docs seem to have a mistake for enabling:

https://github.com/theforeman/foreman-documentation/pull/1118

the 2nd issue, is that the capsule isn't being refreshed after ostree is enabled.  Refreshing the capsule seems to resolve that, will investigate

Upstream bug assigned to ekohlvan

Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/34154 has been resolved.

Verified in Satellite 7/6.11 Snap 14. OS tree getting enabled immediately after the run of installer. this is resolved now, marking as verified.

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 (Moderate: Satellite 6.11 Release), 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-2022:5498