Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1135513 - [RFE] ability to remove puppet module from repository
[RFE] ability to remove puppet module from repository
Status: CLOSED ERRATA
Product: Red Hat Satellite 6
Classification: Red Hat
Component: Content Management (Show other bugs)
6.0.3
Unspecified Unspecified
unspecified Severity medium (vote)
: Unspecified
: Unused
Assigned To: David Davis
Kedar Bidarkar
http://projects.theforeman.org/issues...
: FutureFeature
Depends On:
Blocks: 1139277
  Show dependency treegraph
 
Reported: 2014-08-29 09:47 EDT by David Juran
Modified: 2017-02-23 16:00 EST (History)
13 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-08-12 01:15:34 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 1287653 None None None Never
Red Hat Product Errata RHSA-2015:1592 normal SHIPPED_LIVE Important: Red Hat Satellite 6.1.1 on RHEL 6 2015-08-12 05:04:35 EDT

  None (edit)
Description David Juran 2014-08-29 09:47:16 EDT
Description of problem:
Currently there is no way of removing a puppet module from a repository. Having this ability would be useful

Additional info:
As pointed out by Walden Reines:

You can choose not to include the puppet module when constructing a content view which, for all intents and purposes, is like removing it from the repository.  You can also upload or sync a new version (or a version from a separate publisher) and select that version instead.
Comment 1 RHEL Product and Program Management 2014-08-29 09:53:06 EDT
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.
Comment 3 Andrew Schofield 2014-12-09 14:06:17 EST
I understand the workaround as suggested by Walden but I'd like to know when this will be committed to a release. We really should be able to clear repos out of puppet modules which we may no longer wish for our downstream clients to have any access too.
Comment 4 David Juran 2015-01-07 11:09:51 EST
Clearing needinfo
Comment 6 Mike McCune 2015-01-07 13:43:40 EST
This is actually available upstream and will be shipped with Satellite 6.1, moving to 6.1 release.
Comment 7 Bryan Kearney 2015-01-09 09:43:30 EST
Upstream bug assigned to daviddavis@redhat.com
Comment 8 Bryan Kearney 2015-01-09 10:53:13 EST
Connecting redmine issue http://projects.theforeman.org/issues/5403 from this bug
Comment 9 Bryan Kearney 2015-01-09 10:54:19 EST
Connecting redmine issue http://projects.theforeman.org/issues/5403 from this bug
Comment 10 Bryan Kearney 2015-01-09 10:56:38 EST
The upstream bug is a dupe, but it was fixed by another. I am moving this to POST so that it is moved over when all the other POSTS are moved over.
Comment 13 Kedar Bidarkar 2015-02-13 06:28:36 EST
We can now remove puppet-modules from puppet repos, with the "manage puppet modules" button.

Had synced content from a puppet-link which had 4 puppet modules and then removed 2 puppet modules via the "manage puppet modules" button.

We can see from the below result that the count is now just 2.

---------------
[root@xszas puppet_module]# hammer -u admin -p changeme repository info --id 11 --organization-id 1
/usr/lib/ruby/gems/1.8/gems/hammer_cli-0.1.4/lib/hammer_cli/./apipie/../abstract.rb:68: warning: already initialized constant DEFAULT_LABEL_INDENT
ID:                 11
Name:               puppet_repo
Label:              puppet_repo
Organization:       Default Organization
Red Hat Repository: no
Content Type:       puppet
URL:                http://cxds.fedorapeople.org/repos/random_puppet/
Publish Via HTTP:   yes
Published At:       http://xxxx.redhat.com/pulp/repos/Default_Organization/Library/custom/puppet_prd/puppet_repo
Product:            
    ID:   2
    Name: puppet_prd
GPG Key:            

Sync:               
    Status:         
    Last Sync Date: 2015/02/13 09:34:39
Created:            2015/02/13 09:34:10
Updated:            2015/02/13 09:34:11
Content Counts:     
    Puppet Modules: 2


----------------
removing of puppet-module even with hammer CLI is also now possible.

removed 1 puppet-module via cli.

-------------------

[root@xxxx puppet_module]# hammer -u admin -p changeme repository remove-content --content-ids e96ac298-b2ce-4d1b-a995-b7432d6ffbab --id 11 --organization-id 1
/usr/lib/ruby/gems/1.8/gems/hammer_cli-0.1.4/lib/hammer_cli/./apipie/../abstract.rb:68: warning: already initialized constant DEFAULT_LABEL_INDENT
Repository content removed



[root@xxxx puppet_module]# hammer -u admin -p changeme repository info --id 11 --organization-id 1
/usr/lib/ruby/gems/1.8/gems/hammer_cli-0.1.4/lib/hammer_cli/./apipie/../abstract.rb:68: warning: already initialized constant DEFAULT_LABEL_INDENT
ID:                 11
Name:               puppet_repo
Label:              puppet_repo
Organization:       Default Organization
Red Hat Repository: no
Content Type:       puppet
URL:                http://yy.fedorapeople.org/repos/random_puppet/
Publish Via HTTP:   yes
Published At:       http://xxxx.redhat.com/pulp/repos/Default_Organization/Library/custom/puppet_prd/puppet_repo
Product:            
    ID:   2
    Name: puppet_prd
GPG Key:            

Sync:               
    Status:         
    Last Sync Date: 2015/02/13 09:34:39
Created:            2015/02/13 09:34:10
Updated:            2015/02/13 09:34:11
Content Counts:     
    Puppet Modules: 1


VERIFIED with Sat6.1 Beta SNAP2
Comment 14 Bryan Kearney 2015-02-18 17:06:26 EST
Connecting redmine issue http://projects.theforeman.org/issues/7810 from this bug
Comment 15 Andrew Schofield 2015-05-01 14:00:45 EDT
Confirmed, thanks.
Comment 16 Bryan Kearney 2015-08-11 09:28:32 EDT
This bug is slated to be released with Satellite 6.1.
Comment 17 errata-xmlrpc 2015-08-12 01:15:34 EDT
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-2015:1592

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