Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 1313069

Summary: Remove ostree branches from the API and UI
Product: Red Hat Satellite Reporter: Partha Aji <paji>
Component: Container ManagementAssignee: David Davis <daviddavis>
Status: CLOSED ERRATA QA Contact: Sachin Ghai <sghai>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.2.0CC: bbuckingham, bkearney, cwelton, daviddavis, sghai
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
URL: http://projects.theforeman.org/issues/13955
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-27 09:24:10 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
no ostree "Manage Branches" on ostree repo info page. none

Description Partha Aji 2016-02-29 20:57:48 UTC 
We'll be removing the feature where users will pull individual branches for Katello 3.0.
Comment 1 Partha Aji 2016-02-29 20:57:50 UTC 
Created from redmine issue http://projects.theforeman.org/issues/13955
Comment 2 Partha Aji 2016-02-29 20:57:53 UTC 
Upstream bug assigned to daviddavis
Comment 4 Bryan Kearney 2016-03-02 01:05:44 UTC 
Moving to POST since upstream bug http://projects.theforeman.org/issues/13955 has been closed
-------------
David Davis
Applied in changeset commit:katello|42fc8624e96b26b9d3aff485280964db985e8055.
Comment 6 Sachin Ghai 2016-04-20 11:45:00 UTC 
Hey David, Partha: Please advice what needs to be tested here for verification of this issue ? Thanks.
Comment 7 David Davis 2016-04-22 21:01:27 UTC 
I wouldn't worry to much about testing this. Maybe:

1. Create an ostree repo
2. On the repository info screen and confirm that there's no Manage Branches section taht allows you to edit the branches for an ostree repo.
3. Sync the repo
4. Repeat step 2. Also, make sure you see all the ostree repo branches.
Comment 8 Partha Aji 2016-04-22 21:10:26 UTC 
This commit was in way back and updates to this have already made it in. We now automatically pull all the branches related to a repo when you sync. 
I agree that steps listed verify this bz.
Comment 9 Sachin Ghai 2016-04-29 12:31:57 UTC 
Verified with Satellite6 beta snap9.

I don't see any section named with "Manage Branches" under ostree repo info page. I just can see ostree branch count and can view branches. On creating the ostree repo, branch count set to 0. 

After syncing the repo, I can see ostree branches.
Comment 10 Sachin Ghai 2016-04-29 12:32:51 UTC 
Created attachment 1152277 [details]
no ostree "Manage Branches" on ostree repo info page.
Comment 12 errata-xmlrpc 2016-07-27 09:24:10 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/RHBA-2016:1501