Bug 2183980 - Content Management support missing aarch64 with RHEL 9 [NEEDINFO]
Summary: Content Management support missing aarch64 with RHEL 9
Keywords:
Status: NEW
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Hosts - Content
Version: 6.12.0
Hardware: All
OS: All
unspecified
low
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-04-03 10:25 UTC by Direct Docs Feedback
Modified: 2023-08-09 11:42 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:
mdolezel: needinfo? (bangelic)


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SAT-16901 0 None None None 2023-04-03 10:26:25 UTC

Description Direct Docs Feedback 2023-04-03 10:25:38 UTC
Hello 
aarch64 (arm) is missing here. 
This paragraph let people think managed RHEL server can't be running on ARM; But: 
- We sell skus "RHEL for ARM with Smart Management" 
- the doc about Satellite  overview, state that for Content Management at least, RHEL 9 w/ aarch64 is supported https://access.redhat.com/documentation/en-us/red_hat_satellite/6.12/html/satellite_overview_concepts_and_deployment_considerations/introduction_to_server_planning#sect-Architecture_Supported_Client_Architectures 

So maybe a new bullet point could be relevant here, but stating "with restricted scope"  

Reported by: rh-sa-lserot

https://access.redhat.com/documentation/en-us/red_hat_satellite/6.12/html/managing_hosts/registering_hosts_to_server_managing-hosts#annotations:f60f93f5-8ff8-4937-982b-06185f4fdfcf

Comment 2 Marie Hornickova 2023-04-03 11:53:48 UTC
Hello,

Thank you very much for pointing out this potential gap in documentation.

The BZ will go through regular team triage.

Once the work starts, important updates about the implementation will be shared here.

Thank you!


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