Hi,
when I create new pool in engine, no matter how many wms are specified, it is
created with zero vms. Anyone experiencing similar problem?
Engine commit: 9b82e80
Engine log:
2015-07-08 17:57:44,332 INFO
[org.ovirt.engine.core.bll.AddVmPoolWithVmsCommand]
(org.ovirt.thread.pool-8-thread-29)
- Original Message -
> From: "Omer Frenkel"
> To: "Eli Mesika"
> Cc: "devel"
> Sent: Wednesday, July 8, 2015 4:05:28 PM
> Subject: Re: [ovirt-devel] Reaming VdcFault to EngineFault
>
>
>
> - Original Message -
> > From: "Eli Mesika"
> > To: "devel"
> > Sent: Wednesday, Jul
- Original Message -
> From: "Eli Mesika"
> To: "devel"
> Sent: Wednesday, July 8, 2015 3:56:44 PM
> Subject: Re: [ovirt-devel] Reaming VdcFault to EngineFault
>
>
>
> - Original Message -
> > From: "Eli Mesika"
> > To: "devel"
> > Sent: Wednesday, July 8, 2015 3:22:23 PM
>
- Original Message -
> From: "Eli Mesika"
> To: "devel"
> Sent: Wednesday, July 8, 2015 3:22:23 PM
> Subject: Reaming VdcFault to EngineFault
>
> You may get the following error after rebase with master :
>
> http://pastebin.test.redhat.com/295552
If you can not see this , the error
- Original Message -
> From: "Eyal Edri"
> To: "David Caro"
> Cc: devel@ovirt.org, "infra"
> Sent: Wednesday, July 8, 2015 2:16:53 PM
> Subject: Re: [ovirt-devel] ovirt-engine related fedora 21 builds in jenkins
>
>
>
> - Original Message -
> > From: "David Caro"
> > To: "S
You may get the following error after rebase with master :
http://pastebin.test.redhat.com/295552
The reason is that the CommandEntity has a memeber of type VdcReturnValueBase
which contains
the VdcFault. It is serialized by jackson into the db, and when there is
an attempt to deserialize it - y
- Original Message -
> From: "David Caro"
> To: "Sandro Bonazzola"
> Cc: "infra" , devel@ovirt.org
> Sent: Wednesday, July 8, 2015 3:11:32 PM
> Subject: Re: [ovirt-devel] ovirt-engine related fedora 21 builds in jenkins
>
> On 07/08, Sandro Bonazzola wrote:
> > Hi,
> > while dropping f
On 07/08, Sandro Bonazzola wrote:
> Hi,
> while dropping fc20 builds from master as announced 2 weeks ago[1] I've seen
> that several packages implying ovirt-engine availability on fc21 were
> still built on jenkins also if we dropped fc21 support for 3.6 in favor of
> fc22.
>
> Since there's no
Hi
Please note that the following classes were renamed :
*DAODbFacadeImpl.java => *DaoImpl.java
VdsIdParametersBase => IdQueryableParameter
VdcBllErrors => EngineBllError
VdcBllMessages => EngineBllMessage
VdcFault => EngineFault
Thanks
Eli Mesika
___
Hi,
while dropping fc20 builds from master as announced 2 weeks ago[1] I've seen
that several packages implying ovirt-engine availability on fc21 were
still built on jenkins also if we dropped fc21 support for 3.6 in favor of fc22.
Since there's no commitment from integration team and from infras
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/07/15 09:26, Francesco Romani wrote:
> ... AFAIR, in the patchset which is part of qemu-kvm-ev, a lot of
> devices are disabled for security/safety/auditing reasons, and
> new, stable machines are added (rhel*).
Thanks Franceso and Michal for
On 08-07-2015 4:26, Francesco Romani wrote:
... AFAIR, in the patchset which is part of qemu-kvm-ev, a lot
of devices are disabled for security/safety/auditing reasons,
and new, stable machines are added (rhel*).
When QEMU migrates, again to another qemu or to file, among other
things it needs
- Original Message -
> From: "Sven Kieske"
> To: devel@ovirt.org
> Sent: Wednesday, July 8, 2015 9:08:47 AM
> Subject: Re: [ovirt-devel] [!!Mass Mail]Re: VM won't start because of
> -incoming flag after upgrading to alpha-2
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 07/0
On Jul 8, 2015, at 09:22 , Michal Skrivanek wrote:
>
> On Jul 8, 2015, at 09:08 , Sven Kieske wrote:
>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> On 07/07/15 13:36, Francesco Romani wrote:
>>> but if you suspended on qemu and resumed on qemu-kvm-ev, or vice
>>> versa, then I'm
On Jul 8, 2015, at 09:08 , Sven Kieske wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 07/07/15 13:36, Francesco Romani wrote:
>> but if you suspended on qemu and resumed on qemu-kvm-ev, or vice
>> versa, then I'm not sure this flow is supported (AFAIR, it isn't).
>
> I wonder
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/07/15 13:36, Francesco Romani wrote:
> but if you suspended on qemu and resumed on qemu-kvm-ev, or vice
> versa, then I'm not sure this flow is supported (AFAIR, it isn't).
I wonder why that should not be supported, afaik the only
difference bet
16 matches
Mail list logo
