Bug 1315877 - Ostree Repos should always be protected
Summary: Ostree Repos should always be protected
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: WebUI
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
high vote
Target Milestone: Unspecified
Assignee: Partha Aji
QA Contact: Sachin Ghai
URL: http://projects.theforeman.org/issues...
Whiteboard:
Depends On:
Blocks: 1321771
TreeView+ depends on / blocked
 
Reported: 2016-03-08 20:51 UTC by Partha Aji
Modified: 2019-09-26 17:35 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-27 09:05:15 UTC
Target Upstream Version:


Attachments (Terms of Use)
user won't have option to change protected ostree repo to unprotected mode from repo details page (66.59 KB, image/png)
2016-03-28 11:11 UTC, Sachin Ghai
no flags Details
UI doesn't show option to create ostree repo in unprotected mode (no option to select 'publish via http') (51.14 KB, image/png)
2016-03-28 11:13 UTC, Sachin Ghai
no flags Details


Links
System ID Priority Status Summary Last Updated
Foreman Issue Tracker 14089 None None None 2016-04-22 16:21:36 UTC
Red Hat Product Errata RHBA-2016:1500 normal SHIPPED_LIVE Red Hat Satellite 6.2 Base Libraries 2016-07-27 12:24:38 UTC

Description Partha Aji 2016-03-08 20:51:38 UTC
Pulp doesnot provide the facility to mark ostree repos as unprotected. We need make sure they are always protected
1) Need UI to hide Publish Via Http for ostree
2) Need Repo Details to hide the same
3) Need model to complain if that field gets changed to unprotected.

Comment 1 Partha Aji 2016-03-08 20:51:40 UTC
Created from redmine issue http://projects.theforeman.org/issues/14089

Comment 2 Partha Aji 2016-03-08 20:51:43 UTC
Upstream bug assigned to paji@redhat.com

Comment 4 Bryan Kearney 2016-03-15 20:04:58 UTC
Moving to POST since upstream bug http://projects.theforeman.org/issues/14089 has been closed
-------------
Partha Aji
Applied in changeset commit:katello|82232a3acd9c954c4c3285b626aa81899e0fd7e8.

Comment 5 Sachin Ghai 2016-03-28 11:05:02 UTC
Verified with sat6.2 beta snap5.1

On creating a ostree repo by enabling unprotected mode, hammer raises error:

 ~]# hammer -u admin -p changeme repository create --name f22_ostree --organization-id 1 --product ostree --url https://dl.fedoraproject.org/pub/fedora/linux/atomic/22/ --publish-via-http yes --content-type ostree
Could not create the repository:
  Validation failed: OSTree Repositories cannot be unprotected.
[root@cloud-qe-3 ~]# 


Similar error while updating it:

~]# hammer -u admin -p changeme repository update --id 29 --organization-id 1 --publish-via-http yes
Could not update the repository:
  Validation failed: OSTree Repositories cannot be unprotected.

Comment 6 Sachin Ghai 2016-03-28 11:11:05 UTC
Created attachment 1140821 [details]
user won't have option to change protected ostree repo to unprotected mode from repo details page

Comment 7 Sachin Ghai 2016-03-28 11:13:08 UTC
Created attachment 1140822 [details]
UI doesn't show option to create ostree repo in unprotected mode (no option to select 'publish via http')

Comment 8 Sachin Ghai 2016-03-28 11:13:53 UTC
Moving this bz to verified as per comment 5 6 and 7.

Comment 11 errata-xmlrpc 2016-07-27 09:05:15 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:1500


Note You need to log in before you can comment on or make changes to this bug.