Bug 1370162

Summary: pvscan failed error during installation of RHVH-4.0-20160817.1
Product: Red Hat Enterprise Virtualization Manager Reporter: Maxim Burgerhout <mburgerh>
Component: rhev-hypervisor-ngAssignee: Ryan Barry <rbarry>
Status: CLOSED CURRENTRELEASE QA Contact: Virtualization Bugs <virt-bugs>
Severity: urgent Docs Contact:
Priority: high    
Version: 4.0.0CC: cshao, dfediuck, dguo, fdeutsch, gklein, huiwa, huzhao, jcoscia, leiwang, mburgerh, mhergaar, pvilayat, sbueno, vpodzime, weiwang, yaniwang, ycui
Target Milestone: ovirt-4.0.3   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-08-26 06:16:20 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:
Attachments:
Description Flags
Screenshot of error
none
Screenshot-of-errors none

Description Maxim Burgerhout 2016-08-25 12:19:51 UTC
Description of problem:
During installation of the RHVH ISO image (in a VM, but big enough, with nested virt enabled, etc.) I get the error as in the screenshot.

Error message mentions a failed pvscan on /dev/vda1

Seems related to lvmetad not running. I can get further in the installation when I start lvmetad manually before clicking 'Begin installation'. 

Note: installation fails further in the process, so I still cannot successfully deploy RHVH

Version-Release number of selected component (if applicable):
4.0

How reproducible:


Steps to Reproduce:
1. Download RHV-4.0-20160818.1 from portal
2. Make VM with nested virt and large enough disk
3. Try and install

Actual results:
Installer fails right when physical volumes are created

Expected results:
RHV installs successfully

Additional info:
The VM is not the problem. RHEVH installs fine in it, and so did the beta.

Comment 1 Maxim Burgerhout 2016-08-25 12:20:16 UTC
Created attachment 1193998 [details]
Screenshot of error

Comment 2 Fabian Deutsch 2016-08-25 12:23:38 UTC
Samantha, have you seen this bug before?

Comment 3 Ryan Barry 2016-08-25 12:37:12 UTC
Just to check --

comment#1 says RHV-4.0-20160818.1, but the bug says RHVH-4.0-20160817.1

Can you verify which one this is, please?

I'd also like more information on your nested virt setup here (as much as you can provide). I just tested and cannot reproduce this in a nested environment running on oVirt, but knowing as much as possible about your environment would be helpful.

Comment 4 Javier Coscia 2016-08-25 12:50:16 UTC
Hey there, I'm having the same issue whether I try to install RHVH in GUI or text mode.

The ISO image is RHVH-4.0-20160817.1-RHVH-x86_64-dvd1.iso

I'll be adding some images and logs from /tmp installation

After I start lvm2-lvmetad.socket in a separate shell I was able to finish with the installation.

Regarding the nested setup, I'm working with 3 VMs, 1 being the RHVM, 1 RHV Linux Host and 1 RHVH which is the one failing. The linux host worked just fine

Let me know if you need me to share more information.

Regards
Javier

Comment 9 Maxim Burgerhout 2016-08-25 12:55:23 UTC
(In reply to Ryan Barry from comment #3)
> Just to check --
> 
> comment#1 says RHV-4.0-20160818.1, but the bug says RHVH-4.0-20160817.1
> 
> Can you verify which one this is, please?
> 

Sorry typo in comment#1, correct version is RHVH-4.0-20160817.1-RHVH-x86_64-dvd1.iso

> I'd also like more information on your nested virt setup here (as much as
> you can provide). I just tested and cannot reproduce this in a nested
> environment running on oVirt, but knowing as much as possible about your
> environment would be helpful.

These are VMs under libvirt running on Fedora 24. 
- 30GiB virtio qcow2 disk (also tried with a larger disk)
- Host CPU configuration copied to VM (for nested virt). 
- 8192MiB of memory (also tried with more, up to 14GiB)
- 2 vCPUs (also tried with 4)

I had RHEV3 running in similar VMs before. 

Note: Starting lvmetad doesn't help for me. I end up with a different error regarding tagging thinpool devices. I'll file a separate bug for that if the lvmetad turns out to be the answer and I still see that issue.

Comment 10 Maxim Burgerhout 2016-08-25 12:56:32 UTC
Full trace from anaconda.log:




  File "/usr/lib64/python2.7/site-packages/pyanaconda/threads.py", line 227, in run
    threading.Thread.run(self, *args, **kwargs)

  File "/usr/lib64/python2.7/threading.py", line 764, in run
    self.__target(*self.__args, **self.__kwargs)

  File "/usr/lib64/python2.7/site-packages/pyanaconda/install.py", line 186, in doInstall
    turnOnFilesystems(storage, mountOnly=flags.flags.dirInstall, callbacks=callbacks_reg)

  File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 224, in turnOnFilesystems
    storage.doIt(callbacks)

  File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 374, in doIt
    self.devicetree.processActions(callbacks)

  File "/usr/lib/python2.7/site-packages/blivet/devicetree.py", line 377, in processActions
    action.execute(callbacks)

  File "/usr/lib/python2.7/site-packages/blivet/deviceaction.py", line 568, in execute
    options=self.device.formatArgs)

  File "/usr/lib/python2.7/site-packages/blivet/formats/lvmpv.py", line 136, in create
    lvm.pvscan(self.device)

  File "/usr/lib/python2.7/site-packages/blivet/devicelibs/lvm.py", line 274, in pvscan
    raise LVMError("pvscan failed for %s: %s" % (device, msg))

LVMError: pvscan failed for /dev/vda2: running lvm pvscan --cache --config  devices { preferred_names=["^/dev/mapper/", "^/dev/md/", "^/dev/sd"] }  /dev/vda2 failed

Comment 11 Maxim Burgerhout 2016-08-25 12:57:13 UTC
Accidentally cleared the needinfo for sbueno@

Comment 12 Fabian Deutsch 2016-08-25 12:59:06 UTC
Moving needinfo to Vratislav, as it's blivet.

Comment 15 Pawan kumar Vilayatkar 2016-08-25 13:05:15 UTC
Created attachment 1194016 [details]
Screenshot-of-errors

Comment 17 Vratislav Podzimek 2016-08-25 13:36:29 UTC
Blivet currently relies on lvmetad running. Does it have to be disabled for RHVH installations?

Comment 19 Fabian Deutsch 2016-08-26 06:16:20 UTC
A new iso which is fixing this problem should now be available on the customer portal:

https://access.redhat.com/downloads/content/150/ver=4.0/rhel---7/4.0/x86_64/product-software