Bug 669513

Summary:	Subscription Manager should create a fact called "system.compliant"
Product:	Red Hat Enterprise Linux 6	Reporter:	Bryan Kearney <bkearney>
Component:	subscription-manager	Assignee:	Adrian Likins <alikins>
Status:	CLOSED ERRATA	QA Contact:	John Sefler <jsefler>
Severity:	medium	Docs Contact:
Priority:	low
Version:	6.1	CC:	alikins, jharris, spandey
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-05-19 13:38:52 UTC	Type:	---
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:	639436

Description Bryan Kearney 2011-01-13 20:54:08 UTC

In order for the server to display if a machine is compliant, the subscription-manager tool should store this attribute as a fact and pass it up to the server.

There is currently a "system" collection of facts which contains name and uuid. This fact should be added there.

Comment 2 Adrian Likins 2011-01-17 21:08:06 UTC

commit 7d18fd51056d70d984fa0b950796d92f13d3d2ce
Author: Adrian Likins <alikins>
Date:   Fri Jan 14 11:01:22 2011 -0500

    669513: add a 'system.compliant' fact
    
    Add 'system.compliant' to facts gathering and reporting.
    
    Small change in facts dialog to make sure we show the
    system group twice. Set fact value to True/False

Comment 4 spandey 2011-01-20 12:10:37 UTC

Verified using following subscription-manager rpm 


subscription-manager-firstboot-0.93.13-1.el6.x86_64
subscription-manager-0.93.13-1.el6.x86_64
subscription-manager-gnome-0.93.13-1.el6.x86_64


I am able to find 'system.compliant' facts in facts --list 


[root@beta1 ~]# subscription-manager facts --list | grep system.compliant
system.compliant: False
[root@beta1 ~]# 

Moving defect status from Modified to verified

Comment 5 errata-xmlrpc 2011-05-19 13:38:52 UTC

An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHEA-2011-0611.html