Bug 1972308

Summary: socket facts chart fails to render completely
Product: Red Hat Satellite Reporter: Paul Dudley <pdudley>
Component: FactAssignee: Girija Soni <gisoni>
Status: CLOSED ERRATA QA Contact: visawant
Severity: low Docs Contact: Zuzana Lena Ansorgova <zuansorg>
Priority: low    
Version: 6.9.0CC: casl, gisoni, lstejska, mhulan, shwsingh, zuansorg
Target Milestone: 6.14.0Keywords: FutureFeature, Triaged, UserExperience
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Removed functionality
Doc Text:
.Viewing charts of monitored Facts is removed In the {ProjectWebUI}, the *View Chart* functionality and the *Actions* column are removed from the *Fact Values* table in *Monitor* > *Facts*.
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-11-08 14:17:34 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:
Attachments:
Description Flags
screenshot showing missing field none

Description Paul Dudley 2021-06-15 15:44:36 UTC
Created attachment 1791287 [details]
screenshot showing missing field

Checking Monitor > Facts > searching for 'name = "lscpu::socket(s)"' the chart presented shows 8 fact fields but the chart only renders 7 of those fields. See attached screenshot showing the black field is missing entirely. Mousing over the field reveals nothing (it's missing completely).

Comment 1 Paul Dudley 2021-06-18 16:54:03 UTC
This issue is easily reproducible when trying to render an arc in a fact chart that has values represented in black. Another example from an internal Satellite:
Searching for name = "lscpu::cpu(s)" in monitor > facts yields 6 values, one is represented in black, that value arc is missing entirely and hovering over the value represented in black highlights nothing, though hovering over the other values highlights the respective arc as expected.

Comment 2 Charles Slivkoff 2021-06-18 22:37:21 UTC
This appears to repeat with every 5th value starting with the 6th.

Comment 3 Brad Buckingham 2023-01-04 22:48:23 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 4 Charles Slivkoff 2023-01-05 16:04:41 UTC
If this feature is not expected to work, please consider removing it.

Comment 6 Marek Hulan 2023-01-10 14:58:24 UTC
I agree, we never received much feedback about this functionality and its importance. It seems to fall under the category of "nice to have" and if it does not work reliably (there are some other issues, e.g. filtering after the value is clicked sometimes), we should rather drop it. Therefore I'm going to suggest this one to be kept open, so we use it as a tracker for the removal.

Comment 7 Charles Slivkoff 2023-01-10 14:59:49 UTC
Thank you.

Comment 9 Marek Hulan 2023-02-08 17:20:23 UTC
Created redmine issue https://projects.theforeman.org/issues/36058 from this bug

Comment 10 Bryan Kearney 2023-05-10 08:01:49 UTC
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/36058 has been resolved.

Comment 12 visawant 2023-05-31 12:44:28 UTC
Verified
Satellite version: 6.14.0 Snap 1.0

Steps/observation:
1. Navigate to Monitor > Facts page
2. Actions column and View chart button are not present.
3. Filter is working and Facts Value page is rendering correctly.

Comment 16 errata-xmlrpc 2023-11-08 14:17:34 UTC
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.14 security and bug fix update), 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:6818