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 1478066 - No success message when package is uploaded to repository
Summary: No success message when package is uploaded to repository
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Repositories
Version: 6.3.0
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: Unspecified
Assignee: Walden Raines
QA Contact: Nikhil Kathole
URL: http://projects.theforeman.org/issues...
Whiteboard:
Depends On: 1461831
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-08-03 14:05 UTC by Walden Raines
Modified: 2019-04-01 20:26 UTC (History)
8 users (show)

Fixed In Version: katello-3.4.5
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1461831
Environment:
Last Closed: 2018-02-21 16:32:23 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
screenshot of UI (84.33 KB, image/png)
2017-09-03 05:37 UTC, Nikhil Kathole
no flags Details
screenshot of UI (87.17 KB, image/png)
2017-09-03 05:37 UTC, Nikhil Kathole
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 20569 0 None None None 2017-08-11 21:00:16 UTC

Description Walden Raines 2017-08-03 14:05:30 UTC
Description of problem:

If you upload a package to a repository the packages is uploaded successfully but there is no indication that it has been uploaded.

How reproducible:
Always

Steps to Reproduce:
1. Attempt to upload any package to any yum repo
2. Note lack of success message

Actual results:
No success message

Expected results:
Success message saying the package was uploaded

Comment 3 Walden Raines 2017-08-11 20:18:53 UTC
Created redmine issue http://projects.theforeman.org/issues/20569 from this bug

Comment 4 Walden Raines 2017-08-14 14:14:42 UTC
PR: https://github.com/Katello/katello/pull/6908

Comment 5 Satellite Program 2017-08-16 16:00:27 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/20569 has been resolved.

Comment 6 Nikhil Kathole 2017-09-03 05:36:40 UTC
VERIFIED

Version Tested:
Satellite-6.3 Snap 14

steps:
1. Created product
2. Added yum repository
3. Uploaded package to yum repository 

Successfully displayed the success message as "Successfully uploaded content : ".
(see attached screenshot).

Comment 7 Nikhil Kathole 2017-09-03 05:37:21 UTC
Created attachment 1321429 [details]
screenshot of UI

Comment 8 Nikhil Kathole 2017-09-03 05:37:58 UTC
Created attachment 1321430 [details]
screenshot of UI

Comment 9 Bryan Kearney 2018-02-21 16:32:23 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/RHSA-2018:0336


Note You need to log in before you can comment on or make changes to this bug.