Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1291639 - The "Sync plans" page display incorrect number of repositories in the product
Summary: The "Sync plans" page display incorrect number of repositories in the product
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Repositories
Version: 6.1.2
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Sachin Ghai
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-12-15 11:21 UTC by Ranjan Kumar
Modified: 2020-03-11 15:00 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-27 11:25:11 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
on List/remove tab, repo count is '2' (49.23 KB, image/png)
2016-06-29 07:05 UTC, Sachin Ghai 		no flags Details
View All

Description Ranjan Kumar 2015-12-15 11:21:09 UTC 
Description of problem:
Product tab on the "Sync plans" page display incorrect repository count.

Version-Release number of selected component (if applicable):
Satellite-6.1.2

How reproducible:
Always

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.

Actual results:
Repository count is listed incorrect for the product in the sync plan.

Expected results:
Repository count should be listed correctly.
Comment 3 Brad Buckingham 2016-04-13 19:32:00 UTC 
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.
Comment 4 Sachin Ghai 2016-06-29 07:02:38 UTC 
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.
Comment 6 Sachin Ghai 2016-06-29 07:05:06 UTC 
Created attachment 1173690 [details]
on List/remove tab, repo count is '2'
Comment 7 Bryan Kearney 2016-07-27 11:25:11 UTC 
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:1501
Note You need to log in before you can comment on or make changes to this bug.