RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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 1809234 - Need a robust fact collection method for RHEL8.2 aarch64 server with out using python3-dmidecode
Summary: Need a robust fact collection method for RHEL8.2 aarch64 server with out usi...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: subscription-manager
Version: unspecified
Hardware: aarch64
OS: Unspecified
high
high
Target Milestone: rc
: 9.1
Assignee: Jiri Hnidek
QA Contact: Red Hat subscription-manager QE Team
URL:
Whiteboard:
Depends On: 1804454
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-03-02 16:15 UTC by Rehana
Modified: 2022-11-15 13:13 UTC (History)
10 users (show)

Fixed In Version: subscription-manager-1.29.30-1.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1804454
Environment:
Last Closed: 2022-11-15 11:19:30 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github candlepin subscription-manager pull 3096 0 None Merged Use dmidecode on aarch64 2022-08-05 04:56:46 UTC
Red Hat Product Errata RHBA-2022:8341 0 None None None 2022-11-15 11:19:46 UTC

Comment 6 RHEL Program Management 2022-01-31 07:27:09 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.

Comment 8 Craig Donnelly 2022-08-04 20:51:18 UTC
>> Pre-verification against RHEL 9.0 using scratch subscription-manager-1.29.29-1.git.14.f0056f4.el9.aarch64

[ec2-user@ip-172-31-27-25 ~]$ rpm -q subscription-manager
subscription-manager-1.29.29-1.git.14.f0056f4.el9.aarch64

[ec2-user@ip-172-31-27-25 ~]$ sudo subscription-manager facts | grep -e dmi -e uuid -e socket -e core -e thread -e virt
cpu.core(s)_per_socket: 1
cpu.cpu_socket(s): 1
cpu.thread(s)_per_core: 1
dmi.baseboard.asset_tag: i-045a61d2d6290454e
dmi.baseboard.chassis_handle: 0x0003
dmi.baseboard.contained_object_handles: 0
dmi.baseboard.features: None
dmi.baseboard.manufacturer: Amazon EC2
dmi.baseboard.type: Other
dmi.bios.address: 0xf0000
dmi.bios.bios_revision: 1.0
dmi.bios.release_date: 11/1/2018
dmi.bios.rom_size: 64 kB
dmi.bios.runtime_size: 64 kB
dmi.bios.vendor: Amazon EC2
dmi.bios.version: 1.0
dmi.chassis.asset_tag: Amazon EC2
dmi.chassis.boot-up_state: Safe
dmi.chassis.contained_elements: 0
dmi.chassis.lock: Not Present
dmi.chassis.manufacturer: Amazon EC2
dmi.chassis.number_of_power_cords: 1
dmi.chassis.oem_information: 0x00000000
dmi.chassis.power_supply_state: Safe
dmi.chassis.security_status: None
dmi.chassis.thermal_state: Safe
dmi.chassis.type: Other
dmi.meta.cpu_socket_count: 1
dmi.processor.asset_tag: AWS Graviton
dmi.processor.characteristics: None
dmi.processor.core_count: 1
dmi.processor.core_enabled: 1
dmi.processor.current_speed: 2500 MHz
dmi.processor.family: ARMv8
dmi.processor.id: 83 D0 0F 41 00 00 00 00
dmi.processor.l1_cache_handle: Not Provided
dmi.processor.l2_cache_handle: Not Provided
dmi.processor.l3_cache_handle: Not Provided
dmi.processor.manufacturer: AWS
dmi.processor.max_speed: 2500 MHz
dmi.processor.part_number: AWS Graviton
dmi.processor.serial_number: AWS Graviton
dmi.processor.signature: Implementor 0x41, Variant 0x0, Architecture 15, Part 0xd08, Revision 3
dmi.processor.socket_designation: CPU00
dmi.processor.status: Populated, Enabled
dmi.processor.thread_count: 1
dmi.processor.type: Central Processor
dmi.processor.upgrade: None
dmi.processor.version: AWS Graviton
dmi.system.manufacturer: Amazon EC2
dmi.system.product_name: a1.medium
dmi.system.serial_number: ec207e0a-4f7a-0093-f6bd-ffd8c000a25e
dmi.system.uuid: EC207E0A-4F7A-0093-F6BD-FFD8C000A25E
dmi.system.wake-up_type: Power Switch
lscpu.core(s)_per_socket: 1
lscpu.socket(s): 1
lscpu.thread(s)_per_core: 1
virt.host_type: aws
virt.is_guest: True
virt.uuid: EC207E0A-4F7A-0093-F6BD-FFD8C000A25E

>> DMI Facts look good on aarch64 on AWS

>> Similar found on GCE, minus one issue with virt-what - which was causing sub-man/cloud-what to think the system was Bare Metal -> Unrelated to this change, so filed separately: BZ 2114997
>> virt-what has an update coming in 9.1 that should resolve this issue (BZ 2074476)

>> Auto-Registration works on AWS, and GCE with the virt-what fix.

>> Testing aarch64 is skipped on Azure as it is not available (not currently support, only a tech-preview 8.6 image is available, and 9 images not shipped yet -> was unable to test with the 8.6 image as there was no ARM hardware available to launch).

>> LGTM, pre-verified.

Comment 12 Craig Donnelly 2022-08-22 10:35:33 UTC
>> Verification against build 1.29.30-1.el9

>> Upgrading:

[root@ip-172-31-27-25 ec2-user]# dnf localinstall ./libdnf-plugin-subscription-manager-1.29.30-1.el9.aarch64.rpm ./python3-cloud-what-1.29.30-1.el9.aarch64.rpm ./python3-subscription-manager-rhsm-1.29.30-1.el9.aarch64.rpm ./subscription-manager-1.29.30-1.el9.aarch64.rpm
Updating Subscription Management repositories.
Unable to read consumer identity

This system is not registered with an entitlement server. You can use subscription-manager to register.

Last metadata expiration check: 0:00:34 ago on Mon 22 Aug 2022 10:32:36 AM UTC.
Dependencies resolved.
==================================================================================================================================
 Package                                         Architecture         Version                     Repository                 Size
==================================================================================================================================
Upgrading:
 libdnf-plugin-subscription-manager              aarch64              1.29.30-1.el9               @commandline               85 k
 python3-cloud-what                              aarch64              1.29.30-1.el9               @commandline              101 k
 python3-subscription-manager-rhsm               aarch64              1.29.30-1.el9               @commandline              180 k
 subscription-manager                            aarch64              1.29.30-1.el9               @commandline              903 k

Transaction Summary
==================================================================================================================================
Upgrade  4 Packages

Total size: 1.2 M
Is this ok [y/N]: y
Downloading Packages:
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
  Preparing        :                                                                                                          1/1 
  Upgrading        : python3-cloud-what-1.29.30-1.el9.aarch64                                                                 1/8 
  Upgrading        : python3-subscription-manager-rhsm-1.29.30-1.el9.aarch64                                                  2/8 
  Upgrading        : libdnf-plugin-subscription-manager-1.29.30-1.el9.aarch64                                                 3/8 
  Running scriptlet: subscription-manager-1.29.30-1.el9.aarch64                                                               4/8 
  Upgrading        : subscription-manager-1.29.30-1.el9.aarch64                                                               4/8 
warning: /etc/rhsm/rhsm.conf created as /etc/rhsm/rhsm.conf.rpmnew

  Running scriptlet: subscription-manager-1.29.30-1.el9.aarch64                                                               4/8 
  Running scriptlet: subscription-manager-1.29.26.1-1.el9_0.aarch64                                                           5/8 
  Cleanup          : subscription-manager-1.29.26.1-1.el9_0.aarch64                                                           5/8 
  Running scriptlet: subscription-manager-1.29.26.1-1.el9_0.aarch64                                                           5/8 
  Cleanup          : python3-subscription-manager-rhsm-1.29.26.1-1.el9_0.aarch64                                              6/8 
  Cleanup          : python3-cloud-what-1.29.26.1-1.el9_0.aarch64                                                             7/8 
  Cleanup          : libdnf-plugin-subscription-manager-1.29.26.1-1.el9_0.aarch64                                             8/8 
  Running scriptlet: subscription-manager-1.29.30-1.el9.aarch64                                                               8/8 
  Running scriptlet: libdnf-plugin-subscription-manager-1.29.26.1-1.el9_0.aarch64                                             8/8 
  Verifying        : libdnf-plugin-subscription-manager-1.29.30-1.el9.aarch64                                                 1/8 
  Verifying        : libdnf-plugin-subscription-manager-1.29.26.1-1.el9_0.aarch64                                             2/8 
  Verifying        : python3-cloud-what-1.29.30-1.el9.aarch64                                                                 3/8 
  Verifying        : python3-cloud-what-1.29.26.1-1.el9_0.aarch64                                                             4/8 
  Verifying        : python3-subscription-manager-rhsm-1.29.30-1.el9.aarch64                                                  5/8 
  Verifying        : python3-subscription-manager-rhsm-1.29.26.1-1.el9_0.aarch64                                              6/8 
  Verifying        : subscription-manager-1.29.30-1.el9.aarch64                                                               7/8 
  Verifying        : subscription-manager-1.29.26.1-1.el9_0.aarch64                                                           8/8 
Installed products updated.

Upgraded:
  libdnf-plugin-subscription-manager-1.29.30-1.el9.aarch64               python3-cloud-what-1.29.30-1.el9.aarch64                
  python3-subscription-manager-rhsm-1.29.30-1.el9.aarch64                subscription-manager-1.29.30-1.el9.aarch64              

Complete!

[root@ip-172-31-27-25 ec2-user]# rpm -q subscription-manager
subscription-manager-1.29.30-1.el9.aarch64

>> Checking facts

[root@ip-172-31-27-25 ec2-user]# subscription-manager facts | grep -e dmi -e uuid -e socket -e core -e thread -e virt
cpu.core(s)_per_socket: 1
cpu.cpu_socket(s): 1
cpu.thread(s)_per_core: 1
dmi.baseboard.asset_tag: i-045a61d2d6290454e
dmi.baseboard.chassis_handle: 0x0003
dmi.baseboard.contained_object_handles: 0
dmi.baseboard.features: None
dmi.baseboard.manufacturer: Amazon EC2
dmi.baseboard.type: Other
dmi.bios.address: 0xf0000
dmi.bios.bios_revision: 1.0
dmi.bios.release_date: 11/1/2018
dmi.bios.rom_size: 64 kB
dmi.bios.runtime_size: 64 kB
dmi.bios.vendor: Amazon EC2
dmi.bios.version: 1.0
dmi.chassis.asset_tag: Amazon EC2
dmi.chassis.boot-up_state: Safe
dmi.chassis.contained_elements: 0
dmi.chassis.lock: Not Present
dmi.chassis.manufacturer: Amazon EC2
dmi.chassis.number_of_power_cords: 1
dmi.chassis.oem_information: 0x00000000
dmi.chassis.power_supply_state: Safe
dmi.chassis.security_status: None
dmi.chassis.thermal_state: Safe
dmi.chassis.type: Other
dmi.meta.cpu_socket_count: 1
dmi.processor.asset_tag: AWS Graviton
dmi.processor.characteristics: None
dmi.processor.core_count: 1
dmi.processor.core_enabled: 1
dmi.processor.current_speed: 2500 MHz
dmi.processor.family: ARMv8
dmi.processor.id: 83 D0 0F 41 00 00 00 00
dmi.processor.l1_cache_handle: Not Provided
dmi.processor.l2_cache_handle: Not Provided
dmi.processor.l3_cache_handle: Not Provided
dmi.processor.manufacturer: AWS
dmi.processor.max_speed: 2500 MHz
dmi.processor.part_number: AWS Graviton
dmi.processor.serial_number: AWS Graviton
dmi.processor.signature: Implementor 0x41, Variant 0x0, Architecture 15, Part 0xd08, Revision 3
dmi.processor.socket_designation: CPU00
dmi.processor.status: Populated, Enabled
dmi.processor.thread_count: 1
dmi.processor.type: Central Processor
dmi.processor.upgrade: None
dmi.processor.version: AWS Graviton
dmi.system.manufacturer: Amazon EC2
dmi.system.product_name: a1.medium
dmi.system.serial_number: ec207e0a-4f7a-0093-f6bd-ffd8c000a25e
dmi.system.uuid: EC207E0A-4F7A-0093-F6BD-FFD8C000A25E
dmi.system.wake-up_type: Power Switch
lscpu.core(s)_per_socket: 1
lscpu.socket(s): 1
lscpu.thread(s)_per_core: 1
virt.host_type: aws
virt.is_guest: True
virt.uuid: EC207E0A-4F7A-0093-F6BD-FFD8C000A25E

>> Facts look good with updated virt-what installed:
[root@ip-172-31-27-25 ec2-user]# rpm -q virt-what
virt-what-1.21-2.el9.2.aarch64

>> LGTM from subscription-manager side.

Comment 13 Craig Donnelly 2022-08-22 10:37:13 UTC
Note: incorrect statement in previous comment regarding that virt-what version, that is wrong system and virt-what update is only needed for facts on GCE to work properly.

Comment 15 errata-xmlrpc 2022-11-15 11:19:30 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 (subscription-manager bug fix and enhancement 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/RHBA-2022:8341


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