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 2050217 - Files upload to custom repo does not work properly
Summary: Files upload to custom repo does not work properly
Keywords:
Status: CLOSED DUPLICATE of bug 2037508
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Repositories
Version: 6.11.0
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: 6.11.0
Assignee: satellite6-bugs
QA Contact: Cole Higgins
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-02-03 13:11 UTC by Vladimír Sedmík
Modified: 2022-03-18 14:12 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-02-17 19:00:42 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Vladimír Sedmík 2022-02-03 13:11:07 UTC 
Description of problem:
Files upload to custom repository does not work properly, only first file is loaded.


Version-Release number of selected component (if applicable):
7.0 snap 7


How reproducible:
always


Steps to Reproduce:
1. Create a custom product.
2. Create a custom repo (yum type, defaults, no upstream url) in the product.
3. In the repo page go "Choose Files", select several rpm files, click "Upload".


Actual results:
Success message is displayed (like "Successfully uploaded content:  fox-1.1-2.noarch.rpm, frog-0.1-1.noarch.rpm, giraffe-0.67-2.noarch.rpm")

but Packages count shows "1" (particular package display is blocked by https://bugzilla.redhat.com/show_bug.cgi?id=2035495)

and "Published At" url shows only 1 (the first one) package synced


Expected results:
All files uploaded and published.


Additional info:
When I create a second repo, upload completely different files, I get only one package again, but the one stored in the first repo (not what I provided for the second repo).
No errors seen in production.log nor in journal.
Comment 1 Brad Buckingham 2022-02-03 15:04:13 UTC 
Is this a regression from 6.10?

If the tab is reloaded, does the count get updated?
Comment 2 Vladimír Sedmík 2022-02-04 15:00:09 UTC 
Yes, it is a regression since 6.10.

No, the count still shows 1.
Comment 3 Justin Sherrill 2022-02-17 19:00:42 UTC 
Vlad, i think this may be a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=2037508

I've tested on snap 10 and can't reproduce, so i'll go ahead and close a dupe, but feel free to reopen if you disagree.

*** This bug has been marked as a duplicate of bug 2037508 ***
Comment 4 Vladimír Sedmík 2022-02-21 13:41:26 UTC 
ACK. I'm unable to reproduce at snap 10 too, the issue was obviously fixed in BZ#2037508.
Note You need to log in before you can comment on or make changes to this bug.