Confirmed ovirt-3.2 branch of vdsm does work with migrations.
So there is a difference between it and master as pertains to the migration
logic.
- DHC
On Tue, Feb 5, 2013 at 2:26 PM, Dead Horse <deadhorseconsulting(a)gmail.com>wrote:
Dan,
Building and testing it now.
- DHC
On Tue, Feb 5, 2013 at 2:39 AM, Dan Kenigsberg <danken(a)redhat.com> wrote:
> On Mon, Feb 04, 2013 at 10:38:16AM -0600, Dead Horse wrote:
> > VDSM built from commit: c343e1833f7b6e5428dd90f14f7807dca1baa0b4 works
> > Current VDSM built from master does not work.
> >
> > I could try spending some time trying to bisect and find out where the
> > breakage occurred I suppose.
>
> Would you be kind to find the time to help us here? Clearly, the commit
> on top of c343e1833f7b6e5428dd90f14f7807dca1baa0b4 introduces nasty
> supervdsm regressions; it has to be reverted for any meaningful testing.
> However I do not see how it can be related to the problem at hand.
>
> Would you at least try out the ovirt-3.2 branch (where the infamous
> "zombie reaper" commit is reverted)?
>
> Dan.
>