Bug 978466
| Summary: | subscription-manager fact 'cpu.cpu_socket(s)' is missing in ppc64 and s390x | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | John Sefler <jsefler> |
| Component: | subscription-manager | Assignee: | Adrian Likins <alikins> |
| Status: | CLOSED ERRATA | QA Contact: | IDM QE LIST <seceng-idm-qe-list> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 5.10 | CC: | fsharath, jesusr |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
No description necessary
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-09-30 23:12:11 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: | |||
| Bug Depends On: | |||
| Bug Blocks: | 840995 | ||
|
Description
John Sefler
2013-06-26 16:42:42 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. 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). 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.
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 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 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 |