Bug 1303145 - Need to collect host system-id for ppc64 LPAR guests [NEEDINFO]
Need to collect host system-id for ppc64 LPAR guests
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: subscription-manager (Show other bugs)
Unspecified Unspecified
medium Severity low
: rc
: ---
Assigned To: candlepin-bugs
John Sefler
: Triaged
Depends On:
Blocks: rhsm-ppc64
  Show dependency treegraph
Reported: 2016-01-29 11:40 EST by Adrian Likins
Modified: 2017-12-06 06:31 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2017-12-06 06:31:35 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
vrjain: needinfo? (dlah)

Attachments (Terms of Use)

  None (edit)
Description Adrian Likins 2016-01-29 11:40:57 EST
Description of problem:

On ppc64 systems running as LPAR guests under PowerVM, the identifier
for the host system is available in /proc/device-tree/system-id.

The format is a text file, one line, with the IBM system id for the host
as the content. 

A made up example:


Subscription-manager should collect that fact. Fact name/namespace to
be determined, but something like 'virt.host_system_id'

This could potentially be used in lieu of requiring virt-who to
run against IBM lpar/virt management tools.

Version-Release number of selected component (if applicable):
All versions.

Steps to Reproduce:
1. log into ppc64 lpar
2. subscription-manager facts --list | grep system_id
Comment 4 Jan Kurik 2017-12-06 06:31:35 EST
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.

The official life cycle policy can be reviewed here:


This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:


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