Bug 1135513

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.

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.

Clearing needinfo

This is actually available upstream and will be shipped with Satellite 6.1, moving to 6.1 release.

Upstream bug assigned to daviddavis

Connecting redmine issue http://projects.theforeman.org/issues/5403 from this bug

Connecting redmine issue http://projects.theforeman.org/issues/5403 from this bug

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.

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

Connecting redmine issue http://projects.theforeman.org/issues/7810 from this bug

Confirmed, thanks.

This bug is slated to be released with Satellite 6.1.

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