Bug 2159648

Summary:	[RFE] No of RPMs synced should be seen rather than simply synced or not synced.
Product:	Red Hat Satellite	Reporter:	Vedashree Deshpande <vdeshpan>
Component:	Capsule - Content	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED DUPLICATE	QA Contact:	Vladimír Sedmík <vsedmik>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.10.0	Keywords:	FutureFeature
Target Milestone:	Unspecified
Target Release:	Unused
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-01-10 20:34:55 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Vedashree Deshpande 2023-01-10 09:36:47 UTC

Description of problem:

In RHS 6.9, going through WebUI to Infrastructure -> Capsules -> Content, we could see how many packages are available in every capsule in every Content View and to compare it with Satellite and the other Capsules. 
In RHS 6.10, when we follow the same path, there is no number of RPMs in the Content Views, it is only mentioned that the content is synchronized (or not synchronized) correctly. 

several times the RHS capsule was not synchronized with the main Satellite, Pulp on the capsule has had not the same number of the RPMs as the Satellite. It required a new synchronization of the capsule(s). Without synchronization, the clients had nothing to update when we were launching the command "yum update all", however Satellite showed the erratas to apply on the content host.

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

Actual results:
Only the synced/not synced is shown. 

Expected results:
Details of what content is synced should be shown. 

Additional info:

Comment 1 Brad Buckingham 2023-01-10 20:34:55 UTC

This request appears to be a duplicate of bug 2071097; therefore, closing to track the additional request.

If you disagree that this is a duplicate, please feel free to re-open with appropriate details.

*** This bug has been marked as a duplicate of bug 2071097 ***