Bug 1251936

Summary: Adjust all relevent fields in /etc/os-release and ensure they contain the correct informations
Product: Red Hat Enterprise Virtualization Manager Reporter: Fabian Deutsch <fdeutsch>
Component: ovirt-nodeAssignee: Douglas Schilling Landgraf <dougsland>
Status: CLOSED DUPLICATE QA Contact: Virtualization Bugs <virt-bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.6.0CC: ecohen, gklein, lsurette, ycui
Target Milestone: ---   
Target Release: 3.6.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: node
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-09-17 14:37:56 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Node RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Fabian Deutsch 2015-08-10 11:11:52 UTC
Description of problem:
Currently only a subset of the fields in /etc/os-release is mangled, we should revisit this file and 
1) update all fields
2) make sure that the fields contain the correct value

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Fabian Deutsch 2015-08-10 11:16:03 UTC
Should be along the following lines:


NAME="Red Hat Enterprise Virtualization Hypervisor"
VERSION="7.1 (Maipo)"
ID="rhel"
ID_LIKE="fedora"
VERSION_ID="7.1"
PRETTY_NAME="Red Hat Enterprise Virtualization Hypervisor 7.1"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:redhat:enterprise_linux:7.1:GA:hypervisor7"
HOME_URL="https://www.redhat.com/"
BUG_REPORT_URL="https://bugzilla.redhat.com/"

REDHAT_BUGZILLA_PRODUCT="Red Hat Enterprise Virtualization Manager"
REDHAT_BUGZILLA_PRODUCT_VERSION=3.6
REDHAT_SUPPORT_PRODUCT="Red Hat Enterprise Virtualization"
REDHAT_SUPPORT_PRODUCT_VERSION="3.6"

Comment 3 Fabian Deutsch 2015-09-17 14:37:56 UTC
Let#s stick to the minimum: Only solve bug 1251864

*** This bug has been marked as a duplicate of bug 1251864 ***