Loading...

Type: Bug
Resolution: Unresolved
Priority: Undefined
Fix Version/s: None
Affects Version/s: rhel-10.0
Component/s: subscription-manager
Labels:
None

Regression:
No
Severity:
Low

AssignedTeam:
subs-client-tools-2

Story Points:
None
Blocked:
False
Ready:
False
Blocked Reason:

Hide

None

Show
None
Product Documentation Required:
None
Sprint:
None

Preliminary Testing:
None
Test Coverage:

Automated

ProdDocsReview-CCS:
Unspecified
ProdDocsReview-Dev:
Unspecified
ProdDocsReview-QE:
Unspecified

Experience:
Architecture:

aarch64

PX Impact Score:
SFDC Cases Counter:
SFDC Cases Open:
SFDC Cases Links:

Planning:
None

What were you trying to do that didn't work?

This is essentially a re-opening of Bugzilla 1934312 which was originally opened against rhel-8 and has not yet been fixed by Jira Epic ENT-4522 and continues to fail on rhel-9 and rhel-10.

What is the impact of this issue to you?

The impact has to do with subscription consumption. Some RHEL subscriptions are tightly coupled to system socket counts thereby requiring higher subscription quantities to be attached to systems with higher socket counts. subscription-manager calculates a system fact called "cpu.cpu_socket(s)" which is used for determining the number of subscriptions to consume for the system. However there is also a system fact called "lscpu.socket(s)" which is calculated by the lscpu tool provided by the util-linux component which is more accepted for accuracy. These facts should match. Although the introduction of Simple Content Access makes subscription attachment and quantity consumption obsolete at the rhel-10 system level, higher level tools like Subscription Watch are now being used to track subscription consumption based on registered system facts making this bug still valid.

Please provide the package NVR for which the bug is seen:

[root@hpe-apollo-cn99xx-14-vm-12 ~]# cat /etc/redhat-release 
Red Hat Enterprise Linux release 10.0 (Coughlan)

[root@hpe-apollo-cn99xx-14-vm-12 ~]# rpm -q subscription-manager util-linux
subscription-manager-1.30.6-1.el10_0.aarch64
util-linux-2.40.2-10.el10.aarch64

How reproducible is this bug?:

Steps to reproduce

System Hostname: hpe-apollo-cn99xx-14-vm-12.khw.eng.rdu2.dc.redhat.com
Beaker Compose: Released RHEL-10.0
Beaker Reservation: https://beaker.engineering.redhat.com/jobs/11586068

[root@hpe-apollo-cn99xx-14-vm-12 ~]# subscription-manager facts --list
cpu.core(s)_per_socket: 4
cpu.cpu(s): 4
cpu.cpu_socket(s): 1
cpu.thread(s)_per_core: 1
cpu.topology_source: kernel /sys cpu sibling lists
distribution.id: Coughlan
distribution.name: Red Hat Enterprise Linux
distribution.version: 10.0
distribution.version.modifier: Unknown
dmi.bios.address: 0xe8000
dmi.bios.bios_revision: 0.0
dmi.bios.release_date: 02/06/2015
dmi.bios.rom_size: 64 kB
dmi.bios.runtime_size: 96 kB
dmi.bios.vendor: EFI Development Kit II / OVMF
dmi.bios.version: 0.0.0
dmi.chassis.boot-up_state: Safe
dmi.chassis.contained_elements: 0
dmi.chassis.lock: Not Present
dmi.chassis.manufacturer: QEMU
dmi.chassis.oem_information: 0x00000000
dmi.chassis.power_supply_state: Safe
dmi.chassis.thermal_state: Safe
dmi.chassis.type: Other
dmi.chassis.version: virt-rhel7.6.0
dmi.memory.array_handle: 0x1000
dmi.memory.error_correction_type: Multi-bit ECC
dmi.memory.error_information_handle: Not Provided
dmi.memory.form_factor: DIMM
dmi.memory.location: Other
dmi.memory.locator: DIMM 0
dmi.memory.manufacturer: QEMU
dmi.memory.maximum_capacity: 6 GB
dmi.memory.number_of_devices: 1
dmi.memory.set: None
dmi.memory.size: 6 GB
dmi.memory.type: RAM
dmi.memory.type_detail: Other
dmi.memory.use: System Memory
dmi.meta.cpu_socket_count: 4
dmi.processor.characteristics: None
dmi.processor.core_count: 1
dmi.processor.core_enabled: 1
dmi.processor.current_speed: 2000 MHz
dmi.processor.family: Other
dmi.processor.id: 00 00 00 00 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: QEMU
dmi.processor.max_speed: 2000 MHz
dmi.processor.socket_designation: CPU 3
dmi.processor.status: Populated, Enabled
dmi.processor.thread_count: 1
dmi.processor.type: Central Processor
dmi.processor.upgrade: Other
dmi.processor.version: virt-rhel7.6.0
dmi.system.family: Red Hat Enterprise Linux
dmi.system.manufacturer: QEMU
dmi.system.product_name: KVM Virtual Machine
dmi.system.uuid: 3E09D1FF-C292-4A32-9C45-2DFD6E9CF939
dmi.system.version: virt-rhel7.6.0
dmi.system.wake-up_type: Power Switch
last_boot: 2025-08-26 15:45:10 UTC
lscpu.architecture: aarch64
lscpu.bios_cpu_family: 1
lscpu.bios_model_name: virt-rhel7.6.0  CPU @ 2.0GHz
lscpu.bios_vendor_id: QEMU
lscpu.bogomips: 400.00
lscpu.byte_order: Little Endian
lscpu.cluster(s): 1
lscpu.core(s)_per_cluster: 4
lscpu.cpu(s): 4
lscpu.cpu_op-mode(s): 64-bit
lscpu.flags: fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics cpuid asimdrdm
lscpu.model: 1
lscpu.model_name: ThunderX2-99xx
lscpu.numa_node(s): 1
lscpu.numa_node0_cpu(s): 0-3
lscpu.on-line_cpu(s)_list: 0-3
lscpu.socket(s): 4
lscpu.stepping: 0x1
lscpu.thread(s)_per_core: 1
lscpu.vendor_id: Cavium
lscpu.vulnerability_gather_data_sampling: Not affected
lscpu.vulnerability_itlb_multihit: Not affected
lscpu.vulnerability_l1tf: Not affected
lscpu.vulnerability_mds: Not affected
lscpu.vulnerability_meltdown: Not affected
lscpu.vulnerability_mmio_stale_data: Not affected
lscpu.vulnerability_reg_file_data_sampling: Not affected
lscpu.vulnerability_retbleed: Not affected
lscpu.vulnerability_spec_rstack_overflow: Not affected
lscpu.vulnerability_spec_store_bypass: Mitigation; Speculative Store Bypass disabled via prctl
lscpu.vulnerability_spectre_v1: Mitigation; __user pointer sanitization
lscpu.vulnerability_spectre_v2: Mitigation; Branch predictor hardening
lscpu.vulnerability_srbds: Not affected
lscpu.vulnerability_tsx_async_abort: Not affected
memory.memtotal: 5718160
memory.swaptotal: 6180860
net.interface.enp1s0.ipv4_address: 10.6.6.136
net.interface.enp1s0.ipv4_address_list: 10.6.6.136
net.interface.enp1s0.ipv4_broadcast: 10.6.6.255
net.interface.enp1s0.ipv4_broadcast_list: 10.6.6.255
net.interface.enp1s0.ipv4_netmask: 24
net.interface.enp1s0.ipv4_netmask_list: 24
net.interface.enp1s0.ipv6_address.global: 2620:52:9:1606:5054:ff:fe2a:750c
net.interface.enp1s0.ipv6_address.global_list: 2620:52:9:1606:5054:ff:fe2a:750c
net.interface.enp1s0.ipv6_address.link: fe80::5054:ff:fe2a:750c
net.interface.enp1s0.ipv6_address.link_list: fe80::5054:ff:fe2a:750c
net.interface.enp1s0.ipv6_netmask.global: 64
net.interface.enp1s0.ipv6_netmask.global_list: 64
net.interface.enp1s0.ipv6_netmask.link: 64
net.interface.enp1s0.ipv6_netmask.link_list: 64
net.interface.enp1s0.mac_address: 52:54:00:2a:75:0c
net.interface.lo.ipv4_address: 127.0.0.1
net.interface.lo.ipv4_address_list: 127.0.0.1
net.interface.lo.ipv4_broadcast: Unknown
net.interface.lo.ipv4_broadcast_list: Unknown
net.interface.lo.ipv4_netmask: 8
net.interface.lo.ipv4_netmask_list: 8
net.interface.lo.ipv6_address.host: ::1
net.interface.lo.ipv6_address.host_list: ::1
net.interface.lo.ipv6_netmask.host: 128
net.interface.lo.ipv6_netmask.host_list: 128
network.fqdn: hpe-apollo-cn99xx-14-vm-12.khw.eng.rdu2.dc.redhat.com
network.hostname: hpe-apollo-cn99xx-14-vm-12.khw.eng.rdu2.dc.redhat.com
network.ipv4_address: 10.6.6.136
network.ipv6_address: 2620:52:9:1606:5054:ff:fe2a:750c, fe80::5054:ff:fe2a:750c
proc_cpuinfo.common.bogomips: 400.00
proc_cpuinfo.common.cpu_architecture: 8
proc_cpuinfo.common.cpu_implementer: 0x43
proc_cpuinfo.common.cpu_part: 0x0af
proc_cpuinfo.common.cpu_revision: 1
proc_cpuinfo.common.cpu_variant: 0x1
proc_cpuinfo.common.features: fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics cpuid asimdrdm
proc_stat.btime: 1756223110
system.certificate_version: 3.2
system.default_locale: en_US.UTF-8
uname.machine: aarch64
uname.nodename: hpe-apollo-cn99xx-14-vm-12.khw.eng.rdu2.dc.redhat.com
uname.release: 6.12.0-55.9.1.el10_0.aarch64
uname.sysname: Linux
uname.version: #1 SMP PREEMPT_DYNAMIC Tue Mar 25 14:35:09 UTC 2025
virt.host_type: kvm
virt.is_guest: True
virt.uuid: 3E09D1FF-C292-4A32-9C45-2DFD6E9CF939

Expected results

System facts cpu.cpu_socket(s) and lscpu.socket(s) should match

Actual results

[root@hpe-apollo-cn99xx-14-vm-12 ~]# subscription-manager facts --list | grep -E "cpu.cpu_socket|lscpu.socket"
cpu.cpu_socket(s): 1
lscpu.socket(s): 4

mentioned on

Commit - blocked the following tests on open RHEL-111305 issue against aarch64

Merge request - blocked the following tests on open RHEL-111305 issue against aarch64

Details

Description

What were you trying to do that didn't work?

What is the impact of this issue to you?

Please provide the package NVR for which the bug is seen:

How reproducible is this bug?:

Steps to reproduce

Expected results

Actual results

Attachments

Issue Links

Easy Agile Planning Poker

Activity

People

Dates

Hide