Bug 1303145

Summary: Need to collect host system-id for ppc64 LPAR guests
Product: Red Hat Enterprise Linux 6 Reporter: Adrian Likins <alikins>
Component: subscription-managerAssignee: candlepin-bugs
Status: CLOSED WONTFIX QA Contact: John Sefler <jsefler>
Severity: low Docs Contact:
Priority: medium    
Version: 6.8CC: bcourt, csnyder, dlah, vrjain
Target Milestone: rcKeywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-06 11:31:35 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: 1151596    

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/

Comment 5 Red Hat Bugzilla 2023-09-14 03:16:58 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days