[Users] migrations failing with latest master + vdsm
Michal Skrivanek
mskrivan at redhat.com
Wed Oct 16 05:12:34 UTC 2013
On 15 Oct 2013, at 22:22, Dead Horse <deadhorseconsulting at gmail.com> wrote:
> I just took a look through the vdc_options keys and I only found key entries of "AbortMigrationOnError" for cluster levels 3.0, 3.1, and 3.2 but not 3.3.
Yes, set a new one for 3.3 to false
>
> - DHC
>
>
> On Tue, Oct 15, 2013 at 10:55 AM, Dan Kenigsberg <danken at redhat.com> wrote:
>> On Tue, Oct 15, 2013 at 04:42:11PM +0200, Michal Skrivanek wrote:
>> >
>> > On Oct 15, 2013, at 16:36 , Dead Horse <deadhorseconsulting at gmail.com> wrote:
>> >
>> > > I have been running EL 6.4 hosts in 3.3 mode for quite some time, I only noticed this breakage in the latest master VDSM 4.13.x. Tagged vdsm versions: ovirt-3.3.0 and ovirt-3.3 do work (if not using master which one of these should be used with 3.3 btw?)
>> >
>> > it is correct
>> > I suppose as a workaround you can use engine-config and set AbortMigrationOnError to false for now…
>> > the default should change to false till EL 6.5 comes out, I guess…
>>
>> Global configurable are evil, but yes. Please set it to False by
>> default, until we can require a libvirt version that has it.
>>
>> Dan.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20131016/f7f8bd5d/attachment-0001.html>
More information about the Users
mailing list