Bug 1037976 - Should be better to add a new line at end of the output of grub.conf
Summary: Should be better to add a new line at end of the output of grub.conf
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-node
Version: 3.5
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 3.5.0
Assignee: Joey Boggs
QA Contact: bugs@ovirt.org
URL:
Whiteboard: node
Depends On:
Blocks: 1049183
TreeView+ depends on / blocked
 
Reported: 2013-12-04 08:02 UTC by wanghui
Modified: 2016-02-10 19:39 UTC (History)
15 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1049183 (view as bug list)
Environment:
Last Closed: 2014-07-24 18:12:49 UTC
oVirt Team: Node


Attachments (Terms of Use)

Description wanghui 2013-12-04 08:02:33 UTC
Description of problem:
It should be better to add a new line at the end of the output of grub.conf file.

Version-Release number of selected component (if applicable):
ovirt-node-iso-3.0.3-1.1.fc19.iso
ovirt-node-3.0.3-1.1.fc19.noarch

How reproducible:
100%

Steps to Reproduce:
1. Clean install ovirt-node-iso-3.0.3-1.1.fc19.iso.
2. Check the grub.conf file use #cat /dev/.initramfs/live/grub2/grub.cfg

Actual results:
1. After step2, the output it as follows.
[root@localhost admin]# cat /dev/.initramfs/live/grub2/grub.cfg

#default saved
set timeout 5
#hiddenmenu
menuentry "oVirt Node Hypervisor 3.0.3-1.1.fc19" {
set root=(hd0,3)
search --no-floppy --label Root --set root
linux /vmlinuz0 root=live:LABEL=Root ro rootfstype=auto rootflags=ro rd.live.image rd.live.check rd.lvm=0 crashkernel=128M elevator=deadline quiet max_loop=256 rhgb rd.lunks=0 rd.dm=0
    initrd /initrd0.img
}[root@localhost admin]#  

Expected results:
1. It should be better to add a new line at the end of the output of grub.conf file like the follows.
    initrd /initrd0.img
}
[root@localhost admin]#

Additional info:

Comment 1 Sandro Bonazzola 2014-03-04 09:23:18 UTC
This is an automated message.
Re-targeting all non-blocker bugs still open on 3.4.0 to 3.4.1.


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