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 1931530 - [RFE] [UI]: Config report - Messages filtering after click in Report Status graph
Summary: [RFE] [UI]: Config report - Messages filtering after click in Report Status g...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Fact
Version: 6.9.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Radek Mynar
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-02-22 16:09 UTC by Ondrej Gajdusek
Modified: 2023-01-20 16:30 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-10-28 18:04:20 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Ondrej Gajdusek 2021-02-22 16:09:03 UTC
Description of problem:
Clicking at any of the columns in the Report Status graph on the Config Report page does not apply any filter for the log messages.

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

How reproducible:
always

Steps to Reproduce: (copy&paste from BZ1812227)
1. Click Hosts > All Hosts > {an individual host that has ever run an Ansible role}
2. Click the Reports button to view config reports for this host.
3. Click the Last report item for any Ansible config report (they are the ones with a value of N/A in the Origin column, [see BZ1810600])
4. Scroll to the bottom of the page, find the Report Status chart.
5. Click any chart column (.e.g applied, skipped, etc.)

Actual results:
The WebUI does not change.

Expected results:
The WebUI would take us to all reports matching the status we clicked (applied, skipped, etc.).


Additional info:
There certainly was some sort of behavior after the click as there was a spinner spinning prior to the fix applied in BZ1812227.
This BZ might relate to https://projects.theforeman.org/issues/24351.

Comment 1 Brad Buckingham 2022-09-02 20:25:18 UTC
Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team.  Thank you.

Comment 2 Brad Buckingham 2022-10-28 18:04:20 UTC
Thank you for your interest in Red Hat Satellite. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this feel free to contact your Red Hat Account Team. Thank you.


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