Description of problem: Incorrect "puppet module" count when a content view is added to the composite content view. Version-Release number of selected component (if applicable): Satellite 6.8 How reproducible: 100% Steps to Reproduce: 1. Create a content view and add one puppet module in the CV, publish a new version of the CV. 2. Add this content view in a composite content view. Publish a new version of the CCV as well. 3. It is showing 0 puppet modules on the Satellite web UI -> Content views -> Select CCV -> content views tab. 4. puppet module is added to the CCV but on a content view list/add page, it is showing 0 puppet modules. Actual results: Content view is showing 0 puppet modules. Expected results: Content view should list the correct puppet module count. Additional info: This is working fine in Satellite 6.7.
Hello Team, Do we have any updates on this bugzilla?
Apologies for the delay, but due to future 6.9.z releases being reserved for very high priority issues related to upgrading to 6.10 and 6.10 removing puppet content management, i'm going to close this as WONT_FIX.
Steps to retest: 1. Create a content view and add one puppet module in the CV, publish a new version of the CV. 2. Add this content view in a composite content view. Publish a new version of the CCV as well. 3. Check puppet module on the Satellite web UI -> Content views -> Select CCV -> content views tab. Actual results: Content view is showing 1 puppet modules. Expected results: Content view should list the correct puppet module count. I added 1 puppet module then added 2 more, republish the cv and cvv and they are updated correctly. Check the contentview within the cvv also displays 3 puppet module as expected. Verified on 6.9.9_02 with tfm-rubygem-katello-3.18.1.53-1.el7sat.noarch
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 (Important: Satellite 6.9.9 Async Bug Fix Update), 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-2022:1478