Bug 2185125

Summary: Hardware Model is blank for s390x Architectures in the Satellite GUI.
Product: Red Hat Satellite Reporter: Satyajit Das <sadas>
Component: FactAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED MIGRATED QA Contact: Satellite QE Team <sat-qe-bz-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.12.0CC: visawant
Target Milestone: UnspecifiedKeywords: 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:35 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 Satyajit Das 2023-04-06 22:29:40 UTC
Description of problem:

Hardware Model is blank for s390x architecture in the Satellite GUI. 

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

How reproducible:

100%


Steps to Reproduce:

1. Register an RHEL Host running on IBM Z (s390x Architecture) to the satellite.


Actual results:

Hardware Model is blank for s390x Architectures in the Satellite GUI. 


Expected results:

Expecting the model to show up for s390x Redhat servers registered to the Satellite for the host under the "All Hosts" page.


Additional info:

When Host running on Vmware / KVM is registered to the Satellite, Hardware Model is associated automatically.

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