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.

There are multiples of every module stream showing in both the new and old UI. (see attachment) This is because each module has several 'versions' and 'contexts'. The Katello DB stores the 'context' but not the 'version'.

Targeting an individual module by its context and version is not a common use case, so it was decided it's not needed to show the multiples in the UI.

It was also decided that it's best to store a module's 'version' as well, since that will allow us to show only the latest in the UI.

So the tasks are
1. store a module's version in Katello DB
2. use this info on new host details page to eliminate duplicate table rows on Module streams tab

Created from redmine issue https://projects.theforeman.org/issues/34792

Upstream bug assigned to chrobert

Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/34792 has been resolved.

Verified

Steps:

1) Sync RHEL 8 AppStream
2) Register a RHEL 8 host
3) Upload a package profile to populate the module streams in the UI
4) See that there are no duplicate module streams, such as 389-ds

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.12 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-2022:8506