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 2121957 - When installing a new package, the job is labeled with a job ID and not the package.
Summary: When installing a new package, the job is labeled with a job ID and not the p...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Hosts - Content
Version: 6.12.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: 6.15.0
Assignee: Jeremy Lenz
QA Contact: Cole Higgins
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-08-27 19:07 UTC by Matthew Yee
Modified: 2024-04-23 17:12 UTC (History)
5 users (show)

Fixed In Version: rubygem-katello-4.11.0.4-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-04-23 17:12:31 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 36846 0 Normal New When installing a new package, the job is labeled with a job ID and not the package. 2023-10-19 20:44:57 UTC
Red Hat Issue Tracker SAT-20769 0 None None None 2023-10-13 14:49:45 UTC
Red Hat Product Errata RHSA-2024:2010 0 None None None 2024-04-23 17:12:32 UTC

Description Matthew Yee 2022-08-27 19:07:55 UTC
Description of problem:
When installing a package, the job is labeled with a job ID and not the name of the package being installed.

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

How reproducible:
100%

Steps to Reproduce:
1.Click on host > content > packages 
2.Install something.
3.Go to job status and click on the submitted job.


Actual results:
Job name looks something like this: Install package(s) id ^ (17489)

Expected results:
Install package(s) vim-enhanced

Additional info:

Comment 2 Jeremy Lenz 2023-03-16 20:43:10 UTC
This is because the new host details UI uses the job template 'Install packages by Search' which takes a package search rather than a list of package names.

We can definitely look into making the task name more user-friendly where possible.

Comment 3 Jeremy Lenz 2023-10-19 20:44:56 UTC
Created redmine issue https://projects.theforeman.org/issues/36846 from this bug

Comment 4 Bryan Kearney 2023-10-20 00:01:59 UTC
Upstream bug assigned to jlenz

Comment 5 Bryan Kearney 2023-10-20 00:02:02 UTC
Upstream bug assigned to jlenz

Comment 6 Brad Buckingham 2023-10-30 11:29:29 UTC
Bulk setting Target Milestone = 6.15.0 where sat-6.15.0+ is set.

Comment 16 errata-xmlrpc 2024-04-23 17:12:31 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 (Important: Satellite 6.15.0 release), 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-2024:2010


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