Bug 1296250 - Boot screen shows: "Red Hat Enterprise Virtualization Hypervisor 3.6.1"
Summary: Boot screen shows: "Red Hat Enterprise Virtualization Hypervisor 3.6.1"
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-node
Version: 3.6.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Fabian Deutsch
QA Contact: cshao
URL:
Whiteboard: node
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-06 17:36 UTC by Fabian Deutsch
Modified: 2016-01-28 10:59 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-01-28 10:59:20 UTC
oVirt Team: Node
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Fabian Deutsch 2016-01-06 17:36:17 UTC 
Description of problem:
This might irritate users, because on 3.6.0 GA, 3.6.1 will be shown.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 2 cshao 2016-01-07 07:16:59 UTC 
Hi fabian, 

  We can't reproduce this issue with latest RHEV-H 7.2 for RHEV 3.6.2 (rhev-hypervisor7-7.2-20151229.0). 

Boot screen shows: "Red Hat Enterprise Virtualization Hypervisor (Beta) release 7.2"

Test version:
rhev-hypervisor7-7.2-20151229.0
ovirt-node-3.6.1-1.0.el7ev.noarch

# cat /etc/redhat-release 
Red Hat Enterprise Virtualization Hypervisor (Beta) release 7.2 (20151229.0.el7ev)

 Could you tell us which version can reproduce this issue?

Thanks!
Comment 3 Fabian Deutsch 2016-01-07 10:54:33 UTC 
You will probably see it with the next RHEV-H for 3.6
Comment 4 cshao 2016-01-12 03:34:37 UTC 
Still can't reproduce this issue with rhev-hypervisor7-7.2-20160107.0(ovirt-node-3.6.1-2.0.el7ev.noarch) build.

Boot screen shows: "Red Hat Enterprise Virtualization Hypervisor (Beta) release 7.2"
Comment 5 Fabian Deutsch 2016-01-28 10:59:20 UTC 
So, I was mistaken.
Note You need to log in before you can comment on or make changes to this bug.