Bug 978466 - subscription-manager fact 'cpu.cpu_socket(s)' is missing in ppc64 and s390x
Summary: subscription-manager fact 'cpu.cpu_socket(s)' is missing in ppc64 and s390x
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: subscription-manager
Version: 5.10
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Adrian Likins
QA Contact: IDM QE LIST
URL:
Whiteboard:
Depends On:
Blocks: rhsm-rhel510
TreeView+ depends on / blocked
 
Reported: 2013-06-26 16:42 UTC by John Sefler
Modified: 2021-03-02 23:21 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
No description necessary
Clone Of:
Environment:
Last Closed: 2013-09-30 23:12:11 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2013:1332 0 normal SHIPPED_LIVE subscription-manager bug fix and enhancement update 2013-09-30 22:49:24 UTC

Description John Sefler 2013-06-26 16:42:42 UTC
Description of problem:
The 'cpu.cpu_socket(s)' fact is a very important.  It is used by many RHEL subscriptions to require consumption of multiple subscription quantities by high dollar systems with many many sockets.

Currently on RHEL5 ppc64 and s390x architectures, this facts is not getting populated.  As a result, these high socket systems are being entitled as if they were single socket systems.


Version-Release number of selected component (if applicable):
subscription-manager-1.8.11-1.el5

Here are the facts from a recent run against a RHEL5.10 ppc64 system (Notice no cpu.cpu_socket(s)):
ssh root.eng.brq.redhat.com subscription-manager facts --list
Stdout:
distribution.id: Tikanga
distribution.name: Red Hat Enterprise Linux Server
distribution.version: 5.10
memory.memtotal: 6246912
memory.swaptotal: 8290176
net.interface.eth0.ipv4_address: 10.34.54.46
net.interface.eth0.ipv4_broadcast: 10.34.55.255
net.interface.eth0.ipv4_netmask: 23
net.interface.eth0.ipv6_address.global: 2620:52:0:2236:21a:64ff:fe47:b30e
net.interface.eth0.ipv6_address.link: fe80::21a:64ff:fe47:b30e
net.interface.eth0.ipv6_netmask.global: 64
net.interface.eth0.ipv6_netmask.link: 64
net.interface.eth0.mac_address: 00:1A:64:47:B3:0E
net.interface.lo.ipv4_address: 127.0.0.1
net.interface.lo.ipv4_broadcast: Unknown
net.interface.lo.ipv4_netmask: 8
net.interface.lo.ipv6_address.host: ::1
net.interface.lo.ipv6_netmask.host: 128
net.interface.sit0.ipv4_address: Unknown
net.interface.sit0.ipv4_broadcast: Unknown
net.interface.sit0.ipv4_netmask: Unknown
network.hostname: ibm-js22-vios-03-lp1.rhts.eng.brq.redhat.com
network.ipv4_address: 10.34.54.46
network.ipv6_address: ::1
system.certificate_version: 3.2
system.name: ibm-js22-vios-03-lp1.rhts.eng.brq.redhat.com
system.uuid: c60b8cdb-2992-444b-b4d6-3c419a1c9bd1
uname.machine: ppc64
uname.nodename: ibm-js22-vios-03-lp1.rhts.eng.brq.redhat.com
uname.release: 2.6.18-361.el5
uname.sysname: Linux
uname.version: #1 SMP Fri Jun 14 15:12:32 EDT 2013
virt.host_type: Not Applicable
virt.is_guest: False
Stderr:
ExitCode: 0


Here are the facts from a recent run against a RHEL5.10 s390x system (Notice no cpu.cpu_socket(s)):
ssh root.eng.bos.redhat.com subscription-manager facts --list
Stdout:
distribution.id: Tikanga
distribution.name: Red Hat Enterprise Linux Server
distribution.version: 5.10
memory.memtotal: 508916
memory.swaptotal: 1048568
net.interface.eth0.ipv4_address: 10.16.66.205
net.interface.eth0.ipv4_broadcast: 10.16.71.255
net.interface.eth0.ipv4_netmask: 21
net.interface.eth0.ipv6_address.global: 2620:52:0:1040:de:adff:febe:ef0e
net.interface.eth0.ipv6_address.link: fe80::de:adff:febe:ef0e
net.interface.eth0.ipv6_address.site: fec0:0:a10:4000:de:adff:febe:ef0e
net.interface.eth0.ipv6_netmask.global: 64
net.interface.eth0.ipv6_netmask.link: 64
net.interface.eth0.ipv6_netmask.site: 64
net.interface.eth0.mac_address: 02:DE:AD:BE:EF:0E
net.interface.lo.ipv4_address: 127.0.0.1
net.interface.lo.ipv4_broadcast: Unknown
net.interface.lo.ipv4_netmask: 8
net.interface.lo.ipv6_address.host: ::1
net.interface.lo.ipv6_netmask.host: 128
net.interface.sit0.ipv4_address: Unknown
net.interface.sit0.ipv4_broadcast: Unknown
net.interface.sit0.ipv4_netmask: Unknown
network.hostname: ibm-z10-14.rhts.eng.bos.redhat.com
network.ipv4_address: 10.16.66.205
network.ipv6_address: ::1
system.certificate_version: 3.2
system.name: ibm-z10-14.rhts.eng.bos.redhat.com
system.uuid: 61985931-d8d0-4dcb-adc9-2e20c9dba337
uname.machine: s390x
uname.nodename: ibm-z10-14.rhts.eng.bos.redhat.com
uname.release: 2.6.18-361.el5
uname.sysname: Linux
uname.version: #1 SMP Fri Jun 14 15:14:56 EDT 2013
virt.host_type: ibm_systemz
ibm_systemz-zvm
virt.is_guest: True
virt.uuid: Unknown
Stderr:
ExitCode: 0

Comment 1 RHEL Program Management 2013-06-26 17:09:23 UTC
This request was evaluated by Red Hat Product Management for inclusion
in a Red Hat Enterprise Linux release.  Product Management has
requested further review of this request by Red Hat Engineering, for
potential inclusion in a Red Hat Enterprise Linux release for currently
deployed products.  This request is not yet committed for inclusion in
a release.

Comment 2 Adrian Likins 2013-06-27 17:05:25 UTC
patch in the works for some of this (the missing facts is caused by an assumption when/where /proc/sysinfo exists on these platforms, resulting the "normal" socket counting getting skipped for some of these cases).

Comment 5 Adrian Likins 2013-07-29 18:54:39 UTC
in master:

commit 8294890c06ac3f79d9cafd365bb5c203959519cc
Author: Adrian Likins <alikins>
Date:   Mon Jun 17 14:51:34 2013 -0400

    978466: fix missing socket info s390x/ppc64
    
    Try to better handle system with no topology info
    
    s390/ppc sometimes have pretty limited cpu topology
    info available, especially on rhel5. Try to handle
    those cases.
    
    On s390x systems, that have a "cpu topology" info in
    /proc/sysinfo and populated
    /sys/devivces/system/cpu/cpu*/topology, we defer to
    the latter. This is the scenario for s390x on zvm
    running RHEL6.
    
    Systems running RHEL5 will not have the /sys info
    populated, so fall back to the /proc/sysinfo in
    those cases.
    
    For RHEL5 ppc64 systems with no /sys cpu topology
    exposed, attempt to check cpu/cpuN/physical_id
    for topology info.
    
    If that doesn't have useful info, fallback
    to 1 thread = 1 cpu = 1 core = 1 socket
    
    Added cpu_t.topology_source fact to track how
    client determined cpu topology info.

Comment 7 Sharath Dwaral 2013-08-08 14:16:34 UTC
Version:

# rpm -qa | egrep "subscription-manager|python-rhsm"
subscription-manager-gui-1.8.19-1.el5
python-rhsm-1.8.16-1.el5
subscription-manager-firstboot-1.8.19-1.el5
subscription-manager-migration-1.8.19-1.el5
subscription-manager-1.8.19-1.el5
subscription-manager-debuginfo-1.8.19-1.el5

System: S390X

# subscription-manager facts --list
cpu.core(s)_per_socket: 1
cpu.cpu(s): 2
cpu.cpu_socket(s): 2
cpu.thread(s)_per_core: 1
cpu.topology_source: fallback one socket
distribution.id: Tikanga
distribution.name: Red Hat Enterprise Linux Server
distribution.version: 5.10
memory.memtotal: 508916
memory.swaptotal: 1048568
net.interface.eth0.ipv4_address: 10.16.66.205
net.interface.eth0.ipv4_broadcast: 10.16.71.255
net.interface.eth0.ipv4_netmask: 21
net.interface.eth0.ipv6_address.global: 2620:52:0:1040:de:adff:febe:ef0e
net.interface.eth0.ipv6_address.link: fe80::de:adff:febe:ef0e
net.interface.eth0.ipv6_address.site: fec0:0:a10:4000:de:adff:febe:ef0e
net.interface.eth0.ipv6_netmask.global: 64
net.interface.eth0.ipv6_netmask.link: 64
net.interface.eth0.ipv6_netmask.site: 64
net.interface.eth0.mac_address: 02:DE:AD:BE:EF:0E
net.interface.lo.ipv4_address: 127.0.0.1
net.interface.lo.ipv4_broadcast: Unknown
net.interface.lo.ipv4_netmask: 8
net.interface.lo.ipv6_address.host: ::1
net.interface.lo.ipv6_netmask.host: 128
net.interface.sit0.ipv4_address: Unknown
net.interface.sit0.ipv4_broadcast: Unknown
net.interface.sit0.ipv4_netmask: Unknown
network.hostname: ibm-z10-14.rhts.eng.bos.redhat.com
network.ipv4_address: 10.16.66.205
network.ipv6_address: ::1
system.certificate_version: 3.2
uname.machine: s390x
uname.nodename: ibm-z10-14.rhts.eng.bos.redhat.com
uname.release: 2.6.18-367.el5
uname.sysname: Linux
uname.version: #1 SMP Fri Jul 26 17:43:46 EDT 2013
virt.host_type: ibm_systemz
ibm_systemz-zvm
virt.is_guest: True
virt.uuid: Unknown

Comment 8 Sharath Dwaral 2013-08-09 13:21:39 UTC
Version:

# subscription-manager version
server type: This system is currently not registered.
subscription management server: Unknown
subscription-manager: 1.8.16-1.el5
python-rhsm: 1.8.16-1.el5

Verification:

# uname -m
ppc64

# subscription-manager facts --list
cpu.core(s)_per_socket: 1                        <<<<<<<<
cpu.cpu(s): 8                                    <<<<<<<<
cpu.cpu_socket(s): 8                             <<<<<<<< 
cpu.thread(s)_per_core: 1                        <<<<<<<<
cpu.topology_source: ppc64 physical_package_id   <<<<<<<<
distribution.id: Tikanga
distribution.name: Red Hat Enterprise Linux Server
distribution.version: 5.10
memory.memtotal: 6246912
memory.swaptotal: 8290176
net.interface.eth0.ipv4_address: 10.34.54.46
net.interface.eth0.ipv4_broadcast: 10.34.55.255
net.interface.eth0.ipv4_netmask: 23
net.interface.eth0.ipv6_address.global: 2620:52:0:2236:21a:64ff:fe47:b30e
net.interface.eth0.ipv6_address.link: fe80::21a:64ff:fe47:b30e
net.interface.eth0.ipv6_netmask.global: 64
net.interface.eth0.ipv6_netmask.link: 64
net.interface.eth0.mac_address: 00:1A:64:47:B3:0E
net.interface.lo.ipv4_address: 127.0.0.1
net.interface.lo.ipv4_broadcast: Unknown
net.interface.lo.ipv4_netmask: 8
net.interface.lo.ipv6_address.host: ::1
net.interface.lo.ipv6_netmask.host: 128
net.interface.sit0.ipv4_address: Unknown
net.interface.sit0.ipv4_broadcast: Unknown
net.interface.sit0.ipv4_netmask: Unknown
network.hostname: ibm-js22-vios-03-lp1.rhts.eng.brq.redhat.com
network.ipv4_address: 10.34.54.46
network.ipv6_address: ::1
system.certificate_version: 3.2
uname.machine: ppc64
uname.nodename: ibm-js22-vios-03-lp1.rhts.eng.brq.redhat.com
uname.release: 2.6.18-367.el5
uname.sysname: Linux
uname.version: #1 SMP Fri Jul 26 17:39:16 EDT 2013
virt.host_type: Not Applicable
virt.is_guest: False

Moving bug to VERIFIED

Comment 10 errata-xmlrpc 2013-09-30 23:12:11 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, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2013-1332.html


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