[Yahoo-eng-team] [Bug 1718455] Re: [pike] Nova host disable and Live Migrate all instances fail.

2017-10-10 Thread OpenStack Infra
Reviewed:  https://review.openstack.org/506093
Committed: 
https://git.openstack.org/cgit/openstack/nova/commit/?id=87ca0d8af0d6440a7effd4da9e47321b3a335442
Submitter: Jenkins
Branch:master

commit 87ca0d8af0d6440a7effd4da9e47321b3a335442
Author: Sylvain Bauza 
Date:   Thu Sep 21 10:52:46 2017 +0200

Ensure instance can migrate when launched concurrently

When we fixed the problem in If7da79356174be57481ef246618221e3b2ff8200
we forgot to modify a specific check in select_destinations().

Since _schedule() is returning the correct number of needed hosts but
we were still using the wrong number of instances to verify, the
conditional in select_destinations() was always incorrect.

Note that we needed to modify test.py and fake driver because:

 - _do_check_can_live_migrate_destination was using CONF.host
 - check_can_live_migrate_destination in the fake driver was
   incorrectly trying to set a None value to the object while
   libvirt fixed that earlier (block_migration=None when the
   user specifies block_migration='auto' in the API)
 - pre_live_migration in the fake driver was not returning
   migrate_data, which is passed through live_migration and
   _post_live_migration to set the migration object status

Change-Id: Iff839f3478ebe77bf3e2c4becbe9b9b62fff5035
Closes-Bug: #1718455


** Changed in: nova
   Status: In Progress => Fix Released

-- 
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/1718455

Title:
  [pike] Nova host disable and Live Migrate all instances fail.

Status in OpenStack Compute (nova):
  Fix Released
Status in OpenStack Compute (nova) pike series:
  In Progress

Bug description:
  Disabling a host in horizon and live-migrating instances off fail with
  the following error if the instances are created with a single boot
  command. eg. create 10 cirros instances through the horizon dashboard.
  The instances are all KVM and backed by Cinder Volumes.

  2017-09-19 19:02:30.588 19741 DEBUG nova.scheduler.filter_scheduler
  [req-4268ea83-0657-40cc-961b-f0ae9fb3019e
  385c60230b3f49da930dda4d089eda6b 723aa12337a44f818b6d1e1a59f16e49 -
  default default] There are 1 hosts available but 10 instances
  requested to build. select_destinations /usr/lib/python2.7/dist-
  packages/nova/scheduler/filter_scheduler.py:101

  Steps to reproduce:

  1. Create 10 instances via the horizon dashboard at the same time.
  2. Set a compute host disabled.
  3. Choose the migrate host option and select live-migrate as the method.
  4. The live migration will fail all after passing the scheduler with the 
error above.

  NOTE: Creating 10 separate instances with individual "openstack server
  create" commands or running the launch instance 10 times in horizon
  does not produce the same result and the scheduler will evacuate the
  host as expected.

  Nova version on controller:

  ii  nova-api   2:16.0.0-0ubuntu1~cloud0   
all  OpenStack Compute - API frontend
  ii  nova-common2:16.0.0-0ubuntu1~cloud0   
all  OpenStack Compute - common files
  ii  nova-conductor 2:16.0.0-0ubuntu1~cloud0   
all  OpenStack Compute - conductor service
  ii  nova-consoleauth   2:16.0.0-0ubuntu1~cloud0   
all  OpenStack Compute - Console Authenticator
  ii  nova-novncproxy2:16.0.0-0ubuntu1~cloud0   
all  OpenStack Compute - NoVNC proxy
  ii  nova-placement-api 2:16.0.0-0ubuntu1~cloud0   
all  OpenStack Compute - placement API frontend
  ii  nova-scheduler 2:16.0.0-0ubuntu1~cloud0   
all  OpenStack Compute - virtual machine scheduler
  ii  python-nova2:16.0.0-0ubuntu1~cloud0   
all  OpenStack Compute Python libraries
  ii  python-novaclient

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

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp


[Yahoo-eng-team] [Bug 1718455] Re: [pike] Nova host disable and Live Migrate all instances fail.

2017-09-20 Thread Matt Riedemann
** Also affects: nova/ocata
   Importance: Undecided
   Status: New

** No longer affects: nova/ocata

** Also affects: nova/pike
   Importance: Undecided
   Status: New

** Changed in: nova/pike
   Status: New => Confirmed

** Changed in: nova/pike
   Importance: Undecided => Medium

** Tags added: scheduler

-- 
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/1718455

Title:
  [pike] Nova host disable and Live Migrate all instances fail.

Status in OpenStack Compute (nova):
  Confirmed
Status in OpenStack Compute (nova) pike series:
  Confirmed

Bug description:
  Disabling a host in horizon and live-migrating instances off fail with
  the following error if the instances are created with a single boot
  command. eg. create 10 cirros instances through the horizon dashboard.
  The instances are all KVM and backed by Cinder Volumes.

  2017-09-19 19:02:30.588 19741 DEBUG nova.scheduler.filter_scheduler
  [req-4268ea83-0657-40cc-961b-f0ae9fb3019e
  385c60230b3f49da930dda4d089eda6b 723aa12337a44f818b6d1e1a59f16e49 -
  default default] There are 1 hosts available but 10 instances
  requested to build. select_destinations /usr/lib/python2.7/dist-
  packages/nova/scheduler/filter_scheduler.py:101

  Steps to reproduce:

  1. Create 10 instances via the horizon dashboard at the same time. 
  2. Set a compute host disabled. 
  3. Choose the migrate host option and select live-migrate as the method. 
  4. The live migration will fail all after passing the scheduler with the 
error above. 

  NOTE: Creating 10 separate instances with individual "openstack server
  create" commands or running the launch instance 10 times in horizon
  does not produce the same result and the scheduler will evacuate the
  host as expected.

  Nova version on controller:

  ii  nova-api   2:16.0.0-0ubuntu1~cloud0   
all  OpenStack Compute - API frontend
  ii  nova-common2:16.0.0-0ubuntu1~cloud0   
all  OpenStack Compute - common files
  ii  nova-conductor 2:16.0.0-0ubuntu1~cloud0   
all  OpenStack Compute - conductor service
  ii  nova-consoleauth   2:16.0.0-0ubuntu1~cloud0   
all  OpenStack Compute - Console Authenticator
  ii  nova-novncproxy2:16.0.0-0ubuntu1~cloud0   
all  OpenStack Compute - NoVNC proxy
  ii  nova-placement-api 2:16.0.0-0ubuntu1~cloud0   
all  OpenStack Compute - placement API frontend
  ii  nova-scheduler 2:16.0.0-0ubuntu1~cloud0   
all  OpenStack Compute - virtual machine scheduler
  ii  python-nova2:16.0.0-0ubuntu1~cloud0   
all  OpenStack Compute Python libraries
  ii  python-novaclient

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

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp