Bug 1334713 - The name should be "Red Hat Enterprise Virtualization Hypervisor" on entry of RHEV-H grub
Summary: The name should be "Red Hat Enterprise Virtualization Hypervisor" on entry of...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-node
Classification: oVirt
Component: Build
Version: 4.0
Hardware: Unspecified
OS: Unspecified
medium
high
Target Milestone: ovirt-4.0.0-rc
: ---
Assignee: Fabian Deutsch
QA Contact: Huijuan Zhao
URL:
Whiteboard:
: 1334714 (view as bug list)
Depends On:
Blocks: ovirt-node-ng
TreeView+ depends on / blocked
 
Reported: 2016-05-10 12:01 UTC by Huijuan Zhao
Modified: 2016-07-05 07:56 UTC (History)
9 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-07-05 07:56:04 UTC
oVirt Team: Node
Embargoed:
rule-engine: ovirt-4.0.0+
rule-engine: blocker+
rule-engine: planning_ack+
dfediuck: devel_ack+
ycui: testing_ack+


Attachments (Terms of Use)
screenshot of entry name (39.39 KB, image/png)
2016-05-10 12:01 UTC, Huijuan Zhao
no flags Details
log (5.86 MB, application/x-gzip)
2016-05-10 12:03 UTC, Huijuan Zhao
no flags Details
boot entry in rhev-hypervisor7-ng-4.0-20160608.0 (7.33 KB, image/png)
2016-06-14 07:22 UTC, Huijuan Zhao
no flags Details
kickstart file (366 bytes, text/plain)
2016-06-15 06:14 UTC, Huijuan Zhao
no flags Details


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 57334 0 master MERGED osupdater: Use metadata for boot entry 2016-05-13 15:36:39 UTC

Description Huijuan Zhao 2016-05-10 12:01:52 UTC
Created attachment 1155686 [details]
screenshot of entry name

Description of problem:
The name is "Red Hat Enterprise Linux" on entry of RHEV-H grub, it should be "Red Hat Enterprise Virtualization Hypervisor"

Version-Release number of selected component (if applicable):
rhev-hypervisor7-ng-20160506.0.el7
imgbased-0.6-0.1.el7ev.noarch

How reproducible:
100%


Steps to Reproduce:
1. Install rhev-hypervisor7-ng-3.6-20160506.0.el7
2. Reboot and focus on entry of RHEV-H grub

Actual results:
1. After step2, it shows "Red Hat Enterprise Linux" on entry of RHEV-H grub

Expected results:
2. After step2, it should be "Red Hat Enterprise Virtualization Hypervisor" on entry of RHEV-H grub

Additional info:
No such issue in rhev-hypervisor7-ng-3.6-20160429.0, so this is a regression bug.

Comment 1 Huijuan Zhao 2016-05-10 12:03:18 UTC
Created attachment 1155687 [details]
log

Comment 2 Red Hat Bugzilla Rules Engine 2016-05-10 12:09:08 UTC
This bug report has Keywords: Regression or TestBlocker.
Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP.

Comment 3 Huijuan Zhao 2016-06-14 02:29:43 UTC
Still encounter this bug in rhev-hypervisor7-ng-4.0-20160608.0, it shows as below:

-------------------------------------------------------------
Red Hat Enterprise Linux (3.10.0-327.18.2.el7.x86_64) 7.2
tboot 1.8.1
-------------------------------------------------------------

So this bug is not fixed in rhev-hypervisor7-ng-4.0-20160608.0, I will change the status to ASSIGNED.

Comment 4 Red Hat Bugzilla Rules Engine 2016-06-14 02:29:52 UTC
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.

Comment 5 Fabian Deutsch 2016-06-14 06:44:22 UTC
Huijuan, could you please list all boot entries?

Comment 6 Huijuan Zhao 2016-06-14 07:21:39 UTC
Fabian, Comment 3 has been listed all boot entries, detailed info please refer to attachment "boot entry in rhev-hypervisor7-ng-4.0-20160608.0"

Comment 7 Huijuan Zhao 2016-06-14 07:22:15 UTC
Created attachment 1167791 [details]
boot entry in rhev-hypervisor7-ng-4.0-20160608.0

Comment 8 Fabian Deutsch 2016-06-14 07:45:42 UTC
In the case of comment 7 the installation was wrong.

please provide the kickstart you used for installation.

Comment 9 Huijuan Zhao 2016-06-14 09:53:37 UTC
(In reply to Fabian Deutsch from comment #8)
> In the case of comment 7 the installation was wrong.
> 
> please provide the kickstart you used for installation.
The kickstart is as below:

liveimg --url=http://10.66.10.22:8090/rhevh/rhevh7-ng-36/rhev-hypervisor7-ng-4.0-20160608.0/rhev-hypervisor7-ng-4.0-20160608.0.x86_64.liveimg.squashfs

selinux --enforcing

graphical

Comment 10 Fabian Deutsch 2016-06-14 14:07:39 UTC
The kickstart in comment 9 is not suited for RHEV-H installation.

The kickstart does require a %post section with an imgbase layout --init call

Comment 11 Huijuan Zhao 2016-06-15 06:12:27 UTC
I install NGN with another kickstart which include a %post section with an imgbase layout --init call, and the boot entry is as following:

-------------------------------------------------------------
rhevh7-ng-4.0-0.20160608.0
Red Hat Enterprise Linux (3.10.0-327.18.2.el7.x86_64) 7.2
tboot 1.8.1
-------------------------------------------------------------

1. For the first line "rhevh7-ng-4.0-0.20160608.0", will this be the last layout form? If yes, I will close this bug as normal flow, or I will assign this bug.

2. For the second and third lines issue, Bug 1334714 will track it.

Comment 12 Huijuan Zhao 2016-06-15 06:14:42 UTC
Created attachment 1168162 [details]
kickstart file

Comment 13 Fabian Deutsch 2016-06-15 09:42:15 UTC
Yes, the first entry (rhevh7-ng-4.0-0.20160608.0) is the correct entry for the new layout.
And this entry is correct, we decided to go with the short form, because it will fit on every screen.
The pretty name "Red Hat …" is only show in the post-grub stages.

The additional two entries are a) the original boot entry (probably getting removed, see bug 1334714) b) tboot for trusted boot.

IMO this bug can be verified.

Comment 14 Huijuan Zhao 2016-06-15 09:53:28 UTC
Thank you Fabian.
According to Comment 13 and Comment 11, I will change the status to verified.

Comment 15 Fabian Deutsch 2016-06-15 13:44:52 UTC
*** Bug 1334714 has been marked as a duplicate of this bug. ***

Comment 16 Sandro Bonazzola 2016-07-05 07:56:04 UTC
oVirt 4.0.0 has been released, closing current release.


Note You need to log in before you can comment on or make changes to this bug.