[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, November 26, 2014 7:20:23 PM
> Subject: Re: [ovirt-users] ovirt 3.5 rc2 unable to mount cd on running VM
> 
> On Wed, Nov 26, 2014 at 6:03 PM, Omer Frenkel <ofrenkel at redhat.com> wrote:
> 
> >
> >
> > ----- 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, November 26, 2014 2:13:29 AM
> > > Subject: Re: [ovirt-users] ovirt 3.5 rc2 unable to mount cd on running VM
> > >
> > > On Sun, Sep 28, 2014 at 9:15 AM, Omer Frenkel <ofrenkel at redhat.com>
> > wrote:
> > >
> > > >
> > > >
> > > > 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
> > > >
> > >
> > > Hello,
> > > on final 3.5 (ovirt-engine-3.5.0.1-1.el6.noarch) I still have this
> > problem
> > > attaching CD:
> > >
> > > Error while executing action Change CD: Drive image file could not be
> > found
> > >
> > > How can I test the fix that makes the bugzilla entry in VERIFIED status
> > now?
> > > Is the status to be considered for 3.5.1 or can we have the fix in 3.5
> > too?
> > >
> > > Gianluca
> > >
> >
> > looking at git log the fix should be in the 3.5.0 GA
> > so maybe its something else.. can you share the engine.log and vdsm.log
> > for the time of the failure?
> 
> 
> 
> Created a new CentOS 7 VM and indeed it doesn't show the problem at first
> sight.
> You are right that there was a problem with the ISO Domain going up and
> down (for the moment I stopped iptales on engine and this fixed the
> problem... going to check further)
> 
> The pre-existing one instead (c65new) is ok too now.
> I presume there is nothing to run against db or similar to fix the problem
> for pre-existing VMs, correct?
> Gianluca
> 

right, the fix was done in the engine code, nothing to do in the db.