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.
Description of problem:
We are publishing 2-4 times per year new 'stable' composite contentviews for the clients to access. When we publish we can see in the contentviewversion list new numbers of errata and packages and puppet modules.
The most important change in the new published version isthe change in the errata counters.
We get the question from security and applictions team to provide a list of errata we are going to rollout in the next patch round added.
In our case we use compositecontentviews, but it applies to every contentview as the contentviewversion list is the same.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. Cretae and Publish CV with RHEL7Server repo with a filter on date up 2018-06-01
2. Update the filter date to 2018-10-01
3. Publish CV
4. Goto CVV list and see the errata being changes
5. Ask the question to yourself, which errata are now included (or exlcuded)?
Actual results:
The answer on step 5 is not possible
Expected results:
In the CVV list select both version 1 and version 2 of the CVVs. Click button 'Compare' and it shows a side-by-side compare or the Errata like difference between both CVVs
Additional info:
Hi Peter!
We have identified another RHBZ that seems to address exactly what is requested here.
[ [RFE] Content search: content view compare for all content types ]
https://bugzilla.redhat.com/1241500
Unfortunately, it's private, but I'd keep you informed on the progress.
Point is, we have more information in the other BZ and would therefore prefer to close this one as DUPLICATE, if you don't mind!?
Kind regards,
Oliver
Olivier,
I created this BZ as more precise real-world security-audit related use case of the too generic BZ1212450 that was closed.
if BZ1241500 is not too generic (and therefor too costly to code) and will be implemented in the next versions then this BZ can be closed as a dup
Peter
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.13 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-2023:2097