This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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 2228909 - Improve displayed filter rules info in hammer
Summary: Improve displayed filter rules info in hammer
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Views
Version: 6.14.0
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: stream
Assignee: Chris Roberts
QA Contact: Cole Higgins
URL: https://projects.theforeman.org/issue...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-08-03 15:05 UTC by Vladimír Sedmík
Modified: 2024-06-06 16:26 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-06-06 16:26:01 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 37181 0 Low Closed Improve displayed filter rules info in hammer 2024-04-10 19:01:33 UTC
Github Katello katello pull 10895 0 None open Refs #37181 - Add module stream info to cv filter rules rabl 2024-02-19 20:07:31 UTC
Red Hat Issue Tracker   SAT-19511 0 None Migrated None 2024-06-06 16:26:00 UTC

Description Vladimír Sedmík 2023-08-03 15:05:36 UTC
Description of problem:
`hammer content-view version info --include-applied-filters true` shows new details about the filter rules now. Here are some suggestions for further improvement:

1. Filters always show the `Original packages` and `Original module streams` fields regardless the filter type. `Original packages` should be displayed for RPM filters only and `Original module streams` should be displayed for Module stream filter only.
[root@sat ~]# hammer content-view version info --include-applied-filters true --id 18
...
Has Applied Filters:    yes
Applied Filters:        
...
 5) Id:                      8
    Name:                    Container image tag filter
    Type:                    docker
    Inclusion:               yes
    Original packages:       no    <========
    Original module streams: no    <========
    Rules:                   
     1) Id:                     1
        Name:                   latest
        Content view filter Id: 8

2. Package group filters display pulp api UUID for each rule, which is not very user friendly. Package group name (like in WebUI) might look better.
 2) Id:                      5
    Name:                    Package groups
    Type:                    package_group
    Inclusion:               yes
    Original packages:       no
    Original module streams: no
    Rules:                   
     1) Id:                     1
        UUID:                   /pulp/api/v3/content/rpm/packagegroups/ebf75f01-4ac3-4649-b818-055104a36f57/
        Content view filter Id: 5
     2) Id:                     2
        UUID:                   /pulp/api/v3/content/rpm/packagegroups/e1afd706-c213-4989-9bca-29ee6b1f9a6a/
        Content view filter Id: 5

3. Filter rule info does not provide much useful information for some filter types, like modulemd. It should provide more info.
[root@sat ~]# hammer content-view filter rule info --content-view-filter-id 9 --id 1
Rule ID:   1
Filter ID: 9
Created:   2023/08/03 13:26:48
Updated:   2023/08/03 13:26:48


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


How reproducible:
always


Steps to Reproduce:
1. Run `hammer content-view version info --include-applied-filters true --id <cvv_id>` for some CVV with appropriate filters and rules applied.
2. Run `hammer content-view filter rule info --content-view-filter-id <cvf_id> --id <rule_id>`

Comment 1 Bryan Kearney 2024-02-20 00:18:49 UTC
Upstream bug assigned to chrobert

Comment 2 Bryan Kearney 2024-02-20 00:18:51 UTC
Upstream bug assigned to chrobert

Comment 4 Eric Helms 2024-06-06 16:26:01 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.


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