Bug 2228909

Summary: Improve displayed filter rules info in hammer
Product: Red Hat Satellite Reporter: Vladimír Sedmík <vsedmik>
Component: Content ViewsAssignee: Chris Roberts <chrobert>
Status: CLOSED MIGRATED QA Contact: Cole Higgins <chiggins>
Severity: low Docs Contact:
Priority: unspecified    
Version: 6.14.0CC: chiggins, chrobert, iballou, paji, rlavi, sajha
Target Milestone: streamKeywords: EasyFix, MigratedToJIRA, Triaged, UserExperience
Target Release: Unused   
Hardware: x86_64   
OS: Linux   
URL: https://projects.theforeman.org/issues/37181
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:26:01 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 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.