Created attachment 1198100 [details] /var/log/*.*; /tmp/log; sosreport; grub.cfg; ks Description of problem: Miss RHVH 4.0 version info in Grub. Version-Release number of selected component (if applicable): redhat-virtualization-host-4.0-20160826.0 imgbased-0.8.4-1.el7ev.noarch How reproducible: 100% Steps to Reproduce: 1. Install RHVH via ks file in attachment. 2. Reboot RHVH. 3. Focus on Grub. Actual results: Miss RHVH 4.0 version info in Grub. Expected results: RHVH 4.0 version info can show in Grub. Additional info:
Could you please provide a screenshot of the incorrect entry?
We can check the grub.cfg in attachment to know the incorrect entry without screenshot. There are two entries, one entry is 'Red Hat Enterprise Linux (3.10.0-493.el7.x86_64) 7.2', another entry is 'tboot 1.9.4' as submenu. There is no RHVH entry, probably related to Bug 1373370 - RHVH 4.0_7.3: imgbase check failed.
I requested a screenshot because of bug 1366785, which could indicate that just the wrong grub.cfg is getting updated. Which would mean that the attached grub.cfg is not the one used by grub. Please, in addition to the info in comment 2, provide a screenshot.
Created attachment 1198473 [details] 0826 vs 0817
This strongly appears to be identical to rhbz#1373370 I'm not able to reproduce this. Unfortunately, the anaconda logs are not helpful here (they're still from the build, which I also can't reproduce), but it's clear that the bootloader wasn't updated (rhbz#1373370 occurs because the system is not running on an imgbased layer, as does this). Can you please provide the method used for installation, including the complete kernel cmdline?
Created attachment 1198985 [details] 0826-cmdline ks liveimg --url=http://10.66.10.22:8090/rhvh_ngn/squashimg/redhat-virtualization-host-4.0-20160826.0/redhat-virtualization-host-4.0-20160826.0.x86_64.liveimg.squashfs %post imgbase layout --init %end The same error after add below line. imgbase --experimental volume --create /var 4G
I thought this might be the case... I'll grab the compose 7.3 stage2 to test. However, for this bug (or until there's a distilled 7.3 ISO/RHVH 7.3 anaconda build), I would suggest that you install using stage2 from one of the distilled 7.2 ISOs. This works (and results in an installed 7.3 system), without either of the bugs currently reported on 7.3 (imgbase check failed and no RHVH entry in grub, which are probably the same cause). I'll report back with whatever I find with the 7.3 stage2.
*** Bug 1373370 has been marked as a duplicate of this bug. ***
imgbase initialization fails, because we now expect /var to be a separate volume *before* initialization (as part of osupdater). In order to test with the platform stage2, please change your partitioning section to: reqpart --add-boot part pv.01 --size=42000 --grow volgroup HostVG pv.01 logvol swap --vgname=HostVG --name=swap --fstype=swap --recommended logvol none --vgname=HostVG --name=HostPool --thinpool --size=40000 --grow logvol / --vgname=HostVG --name=root --thin --poolname=HostPool --fsoptions="defaults,discard" --size=6000 logvol /var --vgname=HostVG --name=var --thin --poolname=HostPool --fsoptions="defaults,discard" --size=15000 We're actively working on getting the RHV installclass into platform anaconda. --------------------------------------------------------- In the meantime (for 7.3), I'll update redhat-virtualization-host-productimg to contain the RHV installclass so we can consume platform anaconda directly. I put a product.img (with .buildstamp added so it gets rebranded) here: http://cloud.rbarry.org/product.img If you put it in http://path/to/stage2/images/product.img, anaconda will automatically grab/use it. Then you can use autopartitioning (and exactly the same kickstart as 7.2 builds)
Due to "imgbase check"/"imgbase w"/"imgbase layout" is failed and no RHVH boot entry, this bug will block update from 7.3_4.0 to 7.3_4.0 (from redhat-virtualization-host-4.0-20160826.0 to redhat-virtualization-host-4.0-20160912.1)
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.
(In reply to Huijuan Zhao from comment #10) > Due to "imgbase check"/"imgbase w"/"imgbase layout" is failed and no RHVH > boot entry, this bug will block update from 7.3_4.0 to 7.3_4.0 (from > redhat-virtualization-host-4.0-20160826.0 to > redhat-virtualization-host-4.0-20160912.1) Have you tried with the product.img from comment #9?
(In reply to Ryan Barry from comment #12) > (In reply to Huijuan Zhao from comment #10) > > Due to "imgbase check"/"imgbase w"/"imgbase layout" is failed and no RHVH > > boot entry, this bug will block update from 7.3_4.0 to 7.3_4.0 (from > > redhat-virtualization-host-4.0-20160826.0 to > > redhat-virtualization-host-4.0-20160912.1) > > Have you tried with the product.img from comment #9? Tried according to comment #9, all work well: "imgbase check"/"imgbase w"/"imgbase layout" is ok and there is RHVH boot entry, do not block update anymore. Test steps: 1. After add below partitioning section to ks, the auto installation can successful. reqpart --add-boot part pv.01 --size=42000 --grow volgroup HostVG pv.01 logvol swap --vgname=HostVG --name=swap --fstype=swap --recommended logvol none --vgname=HostVG --name=HostPool --thinpool --size=40000 --grow logvol / --vgname=HostVG --name=root --thin --poolname=HostPool --fsoptions="defaults,discard" --size=6000 logvol /var --vgname=HostVG --name=var --thin --poolname=HostPool --fsoptions="defaults,discard" --size=15000 2. Grub info can show correctly 3. imgbase w -> pass imgbase check -> pass imgbase layout -> pass
Just zstream for now, because it seems ot be related to a missing anaconda build
Can you please test this on the 7.3 distill?
Test version: redhat-virtualization-host-4.0-20161007.0 RHVH-4.0-20161007.0-RHVH-x86_64-dvd1.iso imgbased-0.8.5-0.1.el7ev.noarch Test version 1. Install RHVH via iso. 2. Reboot RHVH. 3. Focus on Grub. Test results: RHVH 4.0 version info can show in Grub. So the bug is fixed, I will verify this bug after "Fixed In Version" area is filled.
Hi Ryan, Could you help to fill "Fixed In Version" area with suitable version info? Thanks.
Verify this bug according #c16.