Bug 2184960

Summary:	Host UI Details has storage unit set to disks not Bytes
Product:	Red Hat Satellite	Reporter:	Ladislav Vasina <lvasina>
Component:	Hosts	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED MIGRATED	QA Contact:	Satellite QE Team <sat-qe-bz-list>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.13.0	CC:	aruzicka
Target Milestone:	Unspecified	Keywords:	EasyFix, MigratedToJIRA, Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
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:12:32 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 Ladislav Vasina 2023-04-06 09:46:02 UTC

Description of problem:
On the Host/Details page see the HW properties card. If you have run the puppet agent on the host you should see the "Storage" value displayed there. This value has units set to "disks" which should be "Bytes" or "B" instead.

Version-Release number of selected component (if applicable):
satellite-6.13.0-6.el8sat.noarch
foreman-3.5.1.10-1.el8sat.noarch
Red Hat Enterprise Linux release 8.7 (Ootpa)

How reproducible:
Every time

Steps to Reproduce:
1. Have a satellite and host with puppet enabled
2. Run puppet agent on the host
3. See HW properties card/storage value unit on the Host/Details page

Actual results:
Storage value has "disks" as a unit.

Expected results:
Storage value should have "Bytes" or "B" as a unit.

Additional info:
Problem is going to be here imo https://github.com/Katello/katello/blob/4134aa440d4de725578a2320e15aae0335cc6182/webpack/components/extensions/HostDetails/DetailsTabCards/HwPropertiesCard.js#L22

Comment 1 Eric Helms 2024-06-06 16:12:32 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.