Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 858200

Summary: [RHEV-H 6.3] The Content of grub.conf didn't keep the same after upgraded from 6.3 old to 6.3 latest via TUI and RHEVM .
Product: Red Hat Enterprise Linux 6 Reporter: haiyang,dong <hadong>
Component: ovirt-nodeAssignee: Fabian Deutsch <fdeutsch>
Status: CLOSED CURRENTRELEASE QA Contact: Virtualization Bugs <virt-bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.3CC: acathrow, bsarathy, chchen, cshao, gouyang, hadong, jboggs, leiwang, mburns, ovirt-maint, tlavigne, ycui
Target Milestone: rcKeywords: TestOnly
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ovirt-node-2.5.0-10.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-02-28 20:23:00 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 863982    
Bug Blocks: 875929    

Description haiyang,dong 2012-09-18 10:09:58 UTC
Description of problem:
The Content of grub.conf didn't keep the same when upgraded from 6.3 old to 6.3 latest via TUI and RHEVM .

[root@localhost redhat]# diff grub.conf.viaTUI grub.conf.viaRHEVM
11a12
>     savedefault


Upgraded from rhev-hypervisor6-6.3-20120815.0.el6_3 to rhev-hypervisor6-6.3-20120913.0.el6_3 via TUI:
[root@localhost admin]# cat /dev/.initramfs/live/grub/grub.conf
default saved
timeout 5
hiddenmenu
title Red Hat Enterprise Virtualization Hypervisor (6.3-20120913.0.el6_3)
    root (hd0,1)
    kernel /vmlinuz0 root=live:LABEL=Root ro rootfstype=ext2 rootflags=ro ksdevice=bootif crashkernel=512M-2G:64M,2G-:128M lang= rd_NO_LUKS rd_NO_LVM kssendmac rd_NO_MD quiet elevator=deadline rhgb rd_NO_DM
    initrd /initrd0.img
title BACKUP RHEV Hypervisor 6.3-20120815.0.el6_3
    root (hd0,2)
    kernel /vmlinuz0 root=live:LABEL=RootBackup ro rootfstype=ext2 rootflags=ro ksdevice=bootif crashkernel=512M-2G:64M,2G-:128M lang= rd_NO_LUKS rd_NO_LVM kssendmac rd_NO_MD quiet elevator=deadline rhgb rd_NO_DM
    initrd /initrd0.img

Upgraded from rhev-hypervisor6-6.3-20120815.0.el6_3 to rhev-hypervisor6-6.3-20120913.0.el6_3 via RHEVM:
[root@localhost admin]# cat /dev/.initramfs/live/grub/grub.conf
default saved
timeout 5
hiddenmenu
title Red Hat Enterprise Virtualization Hypervisor (6.3-20120913.0.el6_3)
    root (hd0,1)
    kernel /vmlinuz0 root=live:LABEL=Root ro rootfstype=ext2 rootflags=ro ksdevice=bootif crashkernel=512M-2G:64M,2G-:128M lang= rd_NO_LUKS rd_NO_LVM kssendmac rd_NO_MD quiet elevator=deadline rhgb rd_NO_DM
    initrd /initrd0.img
title BACKUP RHEV Hypervisor 6.3-20120815.0.el6_3
    root (hd0,2)
    kernel /vmlinuz0 root=live:LABEL=RootBackup ro rootfstype=ext2 rootflags=ro ksdevice=bootif crashkernel=512M-2G:64M,2G-:128M lang= rd_NO_LUKS rd_NO_LVM kssendmac rd_NO_MD quiet elevator=deadline rhgb rd_NO_DM
    initrd /initrd0.img
    savedefault


Version-Release number of selected component (if applicable):
rhev-hypervisor6-6.3-20120913.0.el6_3

How reproducible:
100%

Steps to Reproduce:
1.Upgraded from rhev-hypervisor6-6.3-20120815.0.el6_3 to rhev-hypervisor6-6.3-20120913.0.el6_3 via TUI
2.Check the content of /dev/.initramfs/live/grub/grub.conf
3.Upgraded from rhev-hypervisor6-6.3-20120815.0.el6_3 to rhev-hypervisor6-6.3-20120913.0.el6_3 via RHEVM
4.Check the content of /dev/.initramfs/live/grub/grub.conf

Actual results:
The Content of grub.conf didn't keep the same after upgraded from 6.3 old to 6.3 latest via TUI and RHEVM

Expected results:
The Content of grub.conf should keep the same after upgraded from 6.3 old to 6.3 latest via TUI and RHEVM

Additional info:
The Content of grub.conf keep the same when upgraded from 6.3 old to 6.3 latest via cmdline and RHEVM .

Comment 10 Mike Burns 2012-11-15 14:05:06 UTC
*** Bug 863982 has been marked as a duplicate of this bug. ***

Comment 12 haiyang,dong 2012-12-19 11:07:12 UTC
Need to register rhev-h to RHEV-M to reproduce the bug, but there was a bug 
about "Bug 879148 - vdsm 6.4: Register rhev-h to RHEV-M failed" , so need to
wait for that bug was fixed to retest this one.

Comment 14 haiyang,dong 2013-01-29 12:41:45 UTC
Test version:
rhev-hypervisor6-6.4-20130116.3.0.el6
ovirt-node-2.5.0-15.el6.noarch

upgraded rhev-h from rhev-hypervisor6-6.4-20130116.3.0.el6 to itself via TUI,cmdline and RHEVM .

check that the Content of all grub.conf keep the same, so this bug has been fixed,
change the status into "VERIFIED".

Comment 15 Mike Burns 2013-02-28 20:23:00 UTC
This bug was shipped as part of the RHBA-2013:0556 Errata, but was accidentally omitted from the errata text.  

closing this as CurrentRelease