Red Hat Bugzilla – Bug 1291639
The "Sync plans" page display incorrect number of repositories in the product
Last modified: 2016-07-27 07:25:11 EDT
Description of problem:
Product tab on the "Sync plans" page display incorrect repository count.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create a sync plan
2. Add any product to the sync plan, navigate to Products -> Add -> Select "Red Hat Enterprise Linux Server" product and click on "Add Selected"
3. Navigate to the "List/Remove" under the Products tab of the sync plan.
4. Repository count displayed on the page higher compare to actual.
Repository count is listed incorrect for the product in the sync plan.
Repository count should be listed correctly.
With Satellite 6.2 Beta Snap 7, I am no longer seeing the behavior described; therefore, I am going to move this one to ON_QA for verification.
I was not able to locate a duplicate BZ; therefore, this was likely fixed upstream.
When verifying the bug, I would recommend ensuring that the repository was synced, added to a content view and that the content view was published and promoted. I suspect that the count was previously accounting for the multiple instances of a given repository as it moved through the lifecycle environments.
Verified with sat62 GA snap17.
To reproduce this bz, we synced two repos rhel 7Server, and KS7.2 from "Red Hat Enterprise Linux Server" product. I published and promoted to two different environments
Later, created a sync plan -> products -> add -> "Red Hat Enterprise Linux Server" ( with repository count '2')
Verified on sync plan -> products -> List/remove -> "Red Hat Enterprise Linux Server" ( with repository count '2')
Please see the screenshots for verification.
Created attachment 1173690 [details]
on List/remove tab, repo count is '2'
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.