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 2215586

Summary: [RFE] To manage source rpm in custom repository using Red Hat Satellite web UI.
Product: Red Hat Satellite Reporter: Anand Kulkarni <ankulkar>
Component: RepositoriesAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED MIGRATED QA Contact: Satellite QE Team <sat-qe-bz-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.11.5CC: casl, dsinglet, iballou
Target Milestone: UnspecifiedKeywords: FutureFeature, MigratedToJIRA, 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: 2024-06-06 16:22:24 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 Anand Kulkarni 2023-06-16 16:45:54 UTC
1. Proposed title of this feature request

   Source RPM's are unable to manage from Satellite web UI for the custom repository. 

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

   Currently, cu is unable to add or remove the source RPMs from the custom repository 

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

   Customers, should be able to manage the source RPMs from Satellite web UI to add or remove the source RPMs from custom repository.
    
4. How would the customer like to achieve this? (List the functional requirements here)

   Currently, an alternative way suggested using the hammer commands.

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

   Unknown

6. Does the customer have any specific timeline dependencies and which release would they like to target ?

   No

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


8. List any affected packages or components.
   Unknown

Comment 1 Charles Slivkoff 2023-06-16 17:39:48 UTC
See also 2213911

Uploading SRPMs works and until index_content is initiated, the SRPMs will list as normal "Packages".

Once properly reindexed, the count is correct, but there is no means to remove the SRPMs via the UI.

There is a means to remove the SRPMs via hammer:

~~~
# Get the srpm id you want to delete
hammer srpm list

# Remove the srpm in the repository
hammer repository remove-content --id <repo id> --ids <srpm ids> --content-type srpm
~~~

Comment 2 Eric Helms 2024-06-06 16:22:24 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.