Bug 1303145 - Need to collect host system-id for ppc64 LPAR guests [NEEDINFO]
Summary: Need to collect host system-id for ppc64 LPAR guests
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: subscription-manager
Version: 6.8
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: rc
: ---
Assignee: candlepin-bugs
QA Contact: John Sefler
URL:
Whiteboard:
Depends On:
Blocks: rhsm-ppc64
TreeView+ depends on / blocked
 
Reported: 2016-01-29 16:40 UTC by Adrian Likins
Modified: 2017-12-06 11:31 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-06 11:31:35 UTC
Target Upstream Version:
vrjain: needinfo? (dlah)


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1372108 0 medium CLOSED facts related to the identification of a virtual/physical system on ppc64/ppc64le are conflicting 2021-09-09 12:01:34 UTC

Internal Links: 1372108

Description Adrian Likins 2016-01-29 16:40:57 UTC
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:

"IBM,034242DADA"


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 11:31:35 UTC
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:

http://redhat.com/rhel/lifecycle

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:

https://access.redhat.com/


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