Hide Forgot
Description of problem: Looks like an issue with puppet-modules which are already added in other org. First time, when you add puppet-modules from a URL and synced and add them to CV(content-view), CV clearly shows the module name and its available version. However when you use same URL to add those puppet-modules in another org, then CV does not show those modules under CV -> Puppet-module-> Add New module Version-Release number of selected component (if applicable): Satellite 6.1.6 compose3 How reproducible: always Steps to Reproduce: 1. Create a new org or select default org 2. Add a puppet repo using URL: https://omaciel.fedorapeople.org/random_puppet/ 3. sync the repo, you will see one module 4. create a CV 5. add the puppet-module 6. now create another org 'testorg' 7. Add a puppet repo using same URL as above 8. sync the repo, sync would be success, but module count is zero 9. create a CV 10. add the puppet-module - no module would be visible. Actual results: on re-adding puppet modules from already synced URL in another org, wwouldnt show the puppet-modules Expected results: puppet-modules should be visible. Additional info:
Created attachment 1113513 [details] puppet_module repo synced successfully but module count is 0 on UI
Created attachment 1113514 [details] CV doesn't show anything on adding the same puppet-module
Created attachment 1113515 [details] in first org, puppet-modules are visible
I observed the same behaviour in my setup. The puppet module synced and added to CV in one Org is not even synced in another org. The sync shows success but the module count is 0 in second org.
I observed the same behaviour in my setup Satellite 6.1.6 #c4. The puppet module synced and added to CV in one Org is not even synced in another org. The sync shows success but the module count is 0 in second org.
Issue is not specific for WebUI and can be reproduced in the same way using API directly
I can also confirm that issue is a regression as functionality worked completely fine on 6.1.5 for example.
And as everywhere mentioned - that issue is more problem of Puppet Repositories functionality rather than Content Views one, so it is necessary to concentrate attention on that, but of course, in the final result, it is necessary to verify CV part too.
Created redmine issue http://projects.theforeman.org/issues/13166 from this bug
Upstream bug assigned to jsherril
Upstream bug component is Content Management
Moving to POST since upstream bug http://projects.theforeman.org/issues/13166 has been closed ------------- Justin Sherrill Applied in changeset commit:katello|6f44285bf0dc4e71aa47be12496b8ecac85b648c.
This got missed on a move to ON_QA
Verified this in 6.1.6 compose #5 After syncing a puppet repo and uploading a puppet module to a CV in one org, and subsequently doing the same in another org (using the same repo), I was able to see the puppet module for selection/addition to CV in second org.
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:0052