← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1212478] Re: Scheduler finds new host using targeted live migration

 

Jay, you beat me to the punch on that...by minutes nonetheless.  :-)

I was just further triaging the issue and examining the code, and concur
that RetryFilter is not related to live migration; it's only applicable
for the initial spawn/deploy operation.  Let's hold off on this for now
(I'll cancel) and I'm going to continue to dig into this to see what's
going on, but from what I can tell as per my latest findings, the live
migration code is working as it should: if the destination is passed
into the conductor's live migration task, it doesn't even try to locate
a new host and uses what's passed.

Thanks,
Joe.

** Changed in: nova
       Status: New => Invalid

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1212478

Title:
  Scheduler finds new host using targeted live migration

Status in OpenStack Compute (Nova):
  Invalid

Bug description:
  I'm using the master branch of Havana for the basis of this defect,
  although it's probably existed forever.  :-)

  Scenario
  ----------
  1. Using the RetryFilter
  2. In nova.conf, scheduler_max_attempts = 3 (i.e., the default)
  3. Invoke a live-migration in a multi-host environment via [nova live-migration <vm> <host>], indicating the destination host name that the VM should move to.

  Problem
  ---------
  The issue is that the specified host encountered an error for the live migration, but because RetryFilter was enabled, the "failed" host is added to the "exclusion list", so the VM winds up being migrated elsewhere.  While this type of behavior is desirable for untargeted deployments and relocations (i.e., in which no host is specified), it's problematic when a very specific host is desired.

  In this scenario, the migration ends up "succeeding", albeit it on an
  "unexpected" host.  From an end-user perspective, I think that when
  targeted operations such as this are invoked, the operation should
  fail regardless of whether RetryFilter is enabled.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1212478/+subscriptions