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.
Bug 1473011 - Make ostree plugin enabled by default
Summary: Make ostree plugin enabled by default
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Installation
Version: 6.3.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: Unspecified
Assignee: Partha Aji
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-07-19 20:27 UTC by Partha Aji
Modified: 2019-08-12 16:08 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-02-21 16:51:07 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Partha Aji 2017-07-19 20:27:44 UTC 
OSTree was considered an optional plugin in Satellite 6.2 because we did not have the tooling for el6. However Satellite 6.3 is going to be running on el7 only. We should make OSTree always enabled
Comment 2 Rich Jerrido 2017-07-26 10:37:52 UTC 
Ack. With Satellite 6.3 being EL7 only, it would be a much better user experience and will be consistent with the other content types (yum,puppet,docker,file).
Comment 3 David Caplan 2017-07-26 10:43:11 UTC 
I would advocate making this a default plugin iff there is test automation to confirm that it works as designed.
Comment 4 Sachin Ghai 2017-07-26 10:59:38 UTC 
+1 to have it default. We do have the test automation around this. So far we are installing it post satellite install through automation task. Once it will be default, will revert the change in automation.
Comment 7 Adam Ruzicka 2017-08-30 09:01:50 UTC 
Verified.
Version Tested: Satellite-6.3 Snap 13
Package versions:
satellite-6.3.0-16.0.beta.el7sat.noarch

Installed satellite with only --scenario satellite, bunch of ostree packages got installed. In the web UI I can create ostree repositories and navigate to Content > OSTree branches. There is also /etc/foreman-installer/scenarios.d/satellite.migrations/170731153802-add-ostree.rb which enables ostree unless specifically disabled.

# rpm -qa | grep ostree
python-pulp-ostree-common-1.2.1-3.el7sat.noarch
ostree-2017.7-1.el7.x86_64
pulp-ostree-plugins-1.2.1-3.el7sat.noarch
tfm-rubygem-katello_ostree-3.4.4-1.el7sat.noarch

# ruby <<-END
require 'yaml'
answers = YAML.load(File.read '/etc/foreman-installer/scenarios.d/satellite-answers.yaml')
puts "katello::enable_ostree = #{answers['katello']['enable_ostree']}"
END

katello::enable_ostree = true
Comment 8 Satellite Program 2018-02-21 16:51:07 UTC 
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-2018:0336
Note You need to log in before you can comment on or make changes to this bug.