Bug 1419435

Summary: node upgrade inherits /etc/redhat-release
Product: Red Hat Enterprise Virtualization Manager Reporter: Roman Hodain <rhodain>
Component: ovirt-node-ngAssignee: Ryan Barry <rbarry>
Status: CLOSED DUPLICATE QA Contact: Virtualization Bugs <virt-bugs>
Severity: low Docs Contact:
Priority: unspecified    
Version: 4.0.7CC: dfediuck, gklein
Target Milestone: ovirt-4.1.0-beta   
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-02-06 14:30:52 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 Roman Hodain 2017-02-06 07:04:10 UTC 
Description of problem:
Node upgrade copies over /etc/redhat-release which in some cases can cause confusion. In case of upgrade from RHEL 7.2 to 7.3 the file still contains 7.2 version.

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

How reproducible:
100%

Steps to Reproduce:
1. Modify /etc/redhat-release
2. proceed with upgrade

Actual results:
/etc/redhat-release changes are kept.

Expected results:
New information is included

Additional info:

[root@ng01 ~]# cat /etc/redhat-release /etc/os-release 
Red Hat Enterprise Linux release 7.2
NAME="Red Hat Enterprise Linux"
VERSION="7.3"
VERSION_ID="7.3"
ID="rhel"
ID_LIKE="fedora"
VARIANT="Red Hat Virtualization Host"
VARIANT_ID="ovirt-node"
PRETTY_NAME="Red Hat Virtualization Host 4.0 (el7.3)"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:redhat:enterprise_linux:7.3:GA:hypervisor"
HOME_URL="https://www.redhat.com/"
BUG_REPORT_URL="https://bugzilla.redhat.com/"

# FIXME
REDHAT_BUGZILLA_PRODUCT="Red Hat Virtualization"
REDHAT_BUGZILLA_PRODUCT_VERSION=7.3
REDHAT_SUPPORT_PRODUCT="Red Hat Virtualization"
REDHAT_SUPPORT_PRODUCT_VERSION=7.3
Comment 1 Ryan Barry 2017-02-06 14:30:52 UTC 

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