Bug 1561258
| Summary: | grub2-mkconfig on node produce incorrect grub2.cfg if a local VG is present | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Germano Veit Michel <gveitmic> |
| Component: | ovirt-node-ng | Assignee: | Ryan Barry <rbarry> |
| Status: | CLOSED ERRATA | QA Contact: | jiachen zhang <jiaczhan> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.1.10 | CC: | alex-redhat, bgraveno, cshao, dfediuck, huzhao, mgoldboi, qiyuan, rbarry, sbonazzo, yaniwang, ycui, yzhao |
| Target Milestone: | ovirt-4.2.3 | Flags: | lsvaty:
testing_plan_complete-
|
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | imgbased-1.0.12 | Doc Type: | Bug Fix |
| Doc Text: |
To properly set boot flags if grub2-mkconfig is run, or a new kernel is installed, Red Hat Virtualization Host (RHVH) ships with a custom grub generator. This generator uses a list of all local LVM volume groups to create boot arguments, but systems with local storage domains on separate volume groups are currently present in the list, which could result in incorrect flags being in the grub.conf file. This update enables RHVH grub generators to explicitly look for the RHVH volume group, and ignore others.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-05-15 17:57:47 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
Germano Veit Michel
2018-03-28 00:36:04 UTC
This is definitely not related to a new kernel I can reproduce this bug successfully, and the key step as follow: To creat a vg in kickstart: ### Partitioning ### #ignoredisk --drives=sda zerombr clearpart --all bootloader --location=mbr reqpart --add-boot part pv.01 --ondisk=/dev/sda --size=300000 part pv.02 --ondisk=/dev/sda --size=100000 volgroup rhvh pv.01 --reserved-percent=2 volgroup test pv.02 logvol swap --fstype=swap --name=swap --vgname=rhvh --recommended logvol none --name=pool --vgname=rhvh --thinpool --size=200000 --grow logvol / --fstype=ext4 --name=root --vgname=rhvh --thin --poolname=pool --size=100000 --grow logvol /var --fstype=ext4 --name=var --vgname=rhvh --thin --poolname=pool --size=20000 logvol /data --fstype=xfs --name=data --vgname=test --size=50000 then we will have two vg. Then find the suitable kernal to update it. Test this bug with the version redhat-virtualization-host-4.2-20180507.0 Original Kernel: kernel-3.10.0-862-2.3 After run the command "rpm -Uvh", upgraded the kernel to kernel-3.10.0-862 Follow the steps I got the correct results. So the bug has been fixed successfully. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2018:1524 *** Bug 1583675 has been marked as a duplicate of this bug. *** BZ<2>Jira Resync sync2jira sync2jira |