Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 1383566

Summary: [BUG] Content counts show 0(zero) after uploaded rpms into custom repository
Product: Red Hat Satellite Reporter: Muhammad Selim Jahangir <mjahangi>
Component: RepositoriesAssignee: Brad Buckingham <bbuckingham>
Status: CLOSED DUPLICATE QA Contact: Katello QA List <katello-qa-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.2.2CC: bbuckingham, daviddavis, dhawke, jcallaha, mjahangi, stkachen
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-10-20 20:20:33 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:
Attachments:
Description Flags
Package Count after rpms uploaded none

Description Muhammad Selim Jahangir 2016-10-11 05:42:21 UTC
Created attachment 1209015 [details]
Package Count after rpms uploaded

Description of problem:
After creating custom repository without URL reference, rpms were uploaded but it does not display the uploaded packages under Content Count. It shows 0 (zero).

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

How reproducible: always

Steps to Reproduce:
1. Create a custom product (e.g. test_product)
2. Create a repository (e.g. test_repo)
3. Provide no URL for the repository
4. Select Upload Package
5. Upload successfully

Actual results:
showing package count 0

Expected results:
Should show package count greater than 0, after uploaded rpms

Additional info:
Attached screen shots

Comment 2 Brad Buckingham 2016-10-19 21:03:31 UTC
I performed the same test on a Satellite 6.2.2 and the count was updated.

Were there any errors reported in the logs? (e.g. /var/log/messages, /var/log/foreman/production.log)

Would it be possible to attach the foreman-debug?

If the user closes the repo and re-selects it in the UI, is the count updated?

Comment 3 Stanislav Tkachenko 2016-10-20 12:03:26 UTC
I can see same behavior on Satellite 6.3.0 Snap 4.0 and Satellite 6.2.3.

> If the user closes the repo and re-selects it in the UI, is the count updated?
No. Relogin also doesn't help.

Hammer/API also shows 0 packages. The only way to update count and make packages available is to upload another package via hammer/API.

Comment 5 David Davis 2016-10-20 20:20:33 UTC
Selim and Stanislav, are you in a time zone that's ahead of UTC (e.g. UTC+2)? I think this is the same as https://bugzilla.redhat.com/show_bug.cgi?id=1386670. Let me know if your Satellite installs aren't running on servers in a UTC+ time zone though.

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

Comment 6 Red Hat Bugzilla 2023-09-14 03:32:14 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days