1. Proposed title of this feature request

[RFE] Restore package counts for capsule syncs

3. What is the nature and description of the request?

In previous versions of Red Hat Satellite, the customer was able to go to Infrastructure > Capsules > [capsuleName] > Content and inspect the package counts of the completed capsule syncs.  They used this information to verify that all of their capsules had properly synced their content, and when they saw discrepancies, they manually re-synced them to correct them (see open bugzilla 1982894 for more details on the discrepancy issue).

In Satellite 6.10, they can no longer inspect those counts for discrepancies, and they would like to be able to do so.

4. Why does the customer need this? (List the business requirements here)

The customer is concerned that capsule syncs do not always properly sync their content.  No root cause has been identified, so they need a manual way to detect and cope with that issue.

5. How would the customer like to achieve this? (List the functional requirements here)

Replace the checkmark icon with the number of packages synced in Infrastructure > Capsules > [capsuleName] > Content, such that it looks the same as it did in previous versions of Satellite.

6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.

- perform a capsule sync
- click on Infrastructure > Capsules > [capsuleName] > Content
- observe the numbers

7. Is there already an existing RFE upstream or in Red Hat Bugzilla?

no, but the change made in 6.10 makes it impossible to determine whether or not the issue in bugzilla 1982894 was resolved by the migration to pulp3.

8. Does the customer have any specific time-line dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?

no

9. Is the sales team involved in this request and do they have any additional input?

no

10. List any affected packages or components.

pulp, foreman

11. Would the customer be able to assist in testing this functionality if implemented?

yes