[ovirt-users] ovirt 3.5 rc2 unable to mount cd on running VM

[Omer Frenkel]

----- Original Message -----
> From: "Gianluca Cecchi" <gianluca.cecchi at gmail.com>
> To: "Omer Frenkel" <ofrenkel at redhat.com>
> Cc: "users" <users at ovirt.org>
> Sent: Wednesday, September 24, 2014 8:58:37 PM
> Subject: Re: [ovirt-users] ovirt 3.5 rc2 unable to mount cd on running VM
> 
> On Wed, Sep 24, 2014 at 12:58 PM, Omer Frenkel <ofrenkel at redhat.com> wrote:
> 
> >
> >
> > ----- Original Message -----
> > > From: "Gianluca Cecchi" <gianluca.cecchi at gmail.com>
> > > To: "users" <users at ovirt.org>
> > > Sent: Tuesday, September 23, 2014 1:56:07 AM
> > > Subject: [ovirt-users] ovirt 3.5 rc2 unable to mount cd on running VM
> >
> > > No errors in vdsm.log of host and in VM logfile under
> > /var/log/libvirt/qemu
> > > on hypervisor.
> > >
> >
> > do you see the call for changeCD in vdsm?
> > it looks like the call somehow failed
> > does it happens all the time?
> >
> >
> Hello,
> I have only created a CentOS 6.5 VM and an ubuntu 14.04.1 VM both 64 bit.
> Both have the problem.
> See vdsm.log compressed here:
> https://drive.google.com/file/d/0BwoPbcrMv8mvRzlvcjdzd0Q5Q00/edit?usp=sharing
> 
> mount attempt around 19:47 and I actually see this in vdsm.log; previously
> I searched for ERROR messages only, but it seems it is identified as a
> WARNING level message....):
> 
> Thread-837731::DEBUG::2014-09-24
> 19:47:21,928::__init__::467::jsonrpc.JsonRpcServer::(_serveRequest) Calling
> 'VM.changeCD' in bridge with {u'driveSpec':
> u'/rhev/data-center/mnt/ovirtmgr.localdomain.local:_var_lib_exports_iso/3b23161a-18a3-4cfa-bc78-f4fe2052b19e/images/11111111-1111-1111-1111-111111111111/ovirt-guest-tools-3.5_5.iso',
> u'vmID': u'168470b1-b7eb-4dab-8fa4-6b744e2ad738'}
> Thread-837731::INFO::2014-09-24
> 19:47:21,931::clientIF::331::vds::(prepareVolumePath) prepared volume path:
> /rhev/data-center/mnt/ovirtmgr.localdomain.local:_var_lib_exports_iso/3b23161a-18a3-4cfa-bc78-f4fe2052b19e/images/11111111-1111-1111-1111-111111111111/ovirt-guest-tools-3.5_5.iso
> Thread-837731::WARNING::2014-09-24
> 19:47:21,951::clientIF::361::vds::(teardownVolumePath) Drive is not a vdsm
> image: None
> Traceback (most recent call last):
>   File "/usr/share/vdsm/clientIF.py", line 354, in teardownVolumePath
>     if vm.isVdsmImage(drive):
>   File "/usr/share/vdsm/virt/vm.py", line 112, in isVdsmImage
>     return all(k in drive for k in required)
>   File "/usr/share/vdsm/virt/vm.py", line 112, in <genexpr>
>     return all(k in drive for k in required)
> TypeError: argument of type 'NoneType' is not iterable
> 

There is an open bug on that
Bug 1145728 - change cd fail on 'Drive is not a vdsm image'
https://bugzilla.redhat.com/show_bug.cgi?id=1145728

> 
> I see also these kind of messages
> 
> Thread-838408::WARNING::2014-09-24
> 19:57:20,583::Bridge::210::root::(_typeFixup) Fixing up type VmDevice
> Thread-838408::WARNING::2014-09-24
> 19:57:20,583::Bridge::448::root::(fieldClone) fieldClone: type -> deviceType
> Thread-838408::WARNING::2014-09-24
> 19:57:20,583::Bridge::210::root::(_typeFixup) Fixing up type VmDevice
> Thread-838408::WARNING::2014-09-24
> 19:57:20,583::Bridge::448::root::(fieldClone) fieldClone: type -> deviceType
> Thread-838408::WARNING::2014-09-24
> 19:57:20,583::Bridge::210::root::(_typeFixup) Fixing up type VmDevice
> Thread-838408::WARNING::2014-09-24
> 19:57:20,584::Bridge::448::root::(fieldClone) fieldClone: type -> deviceType
> Thread-838408::WARNING::2014-09-24
> 19:57:20,584::Bridge::210::root::(_typeFixup) Fixing up type VmDevice
> Thread-838408::WARNING::2014-09-24
> 19:57:20,584::Bridge::448::root::(fieldClone) fieldClone: type -> deviceType
> Thread-838408::WARNING::2014-09-24
> 19:57:20,584::Bridge::210::root::(_typeFixup) Fixing up type VmDevice
> Thread-838408::WARNING::2014-09-24
> 19:57:20,584::Bridge::448::root::(fieldClone) fieldClone: type -> deviceType
> Thread-838408::WARNING::2014-09-24
> 19:57:20,585::Bridge::210::root::(_typeFixup) Fixing up type VmDevice
> Thread-838408::WARNING::2014-09-24
> 19:57:20,585::Bridge::448::root::(fieldClone) fieldClone: type -> deviceType
> Thread-838408::WARNING::2014-09-24
> 19:57:20,585::Bridge::210::root::(_typeFixup) Fixing up type VmDevice
> Thread-838408::WARNING::2014-09-24
> 19:57:20,585::Bridge::448::root::(fieldClone) fieldClone: type -> deviceType
> Thread-838408::WARNING::2014-09-24
> 19:57:20,585::Bridge::210::root::(_typeFixup) Fixing up type VmDevice
> Thread-838408::WARNING::2014-09-24
> 19:57:20,586::Bridge::448::root::(fieldClone) fieldClone: type -> deviceType
> Thread-838408::WARNING::2014-09-24
> 19:57:20,586::Bridge::210::root::(_typeFixup) Fixing up type VmDevice
> Thread-838408::WARNING::2014-09-24
> 19:57:20,586::Bridge::448::root::(fieldClone) fieldClone: type -> deviceType
> Thread-838408::WARNING::2014-09-24
> 19:57:20,586::Bridge::210::root::(_typeFixup) Fixing up type VmDevice
> Thread-838408::WARNING::2014-09-24
> 19:57:20,586::Bridge::448::root::(fieldClone) fieldClone: type -> deviceType
> Thread-838408::WARNING::2014-09-24
> 19:57:20,586::Bridge::210::root::(_typeFixup) Fixing up type VmDevice
> Thread-838408::WARNING::2014-09-24
> 19:57:20,587::Bridge::448::root::(fieldClone) fieldClone: type -> deviceType
> Thread-838408::WARNING::2014-09-24
> 19:57:20,587::Bridge::210::root::(_typeFixup) Fixing up type VmDevice
> Thread-838408::WARNING::2014-09-24
> 19:57:20,587::Bridge::448::root::(fieldClone) fieldClone: type -> deviceType
> Thread-838408::WARNING::2014-09-24
> 19:57:20,587::Bridge::210::root::(_typeFixup) Fixing up type VmDevice
> Thread-838408::WARNING::2014-09-24
> 19:57:20,587::Bridge::448::root::(fieldClone) fieldClone: type -> deviceType
> Thread-838408::WARNING::2014-09-24
> 19:57:20,588::Bridge::210::root::(_typeFixup) Fixing up type VmDevice
> Thread-838408::WARNING::2014-09-24
> 19:57:20,588::Bridge::448::root::(fieldClone) fieldClone: type -> deviceType
>