← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1737172] [NEW] Resize on same host in multiple-compute nodes environment not possible

 

Public bug reported:

Hi,

On Ocata release, nova 15.0.7( Libvirt+KVM) its not possible to resize working instance on the same host, in multiple compute nodes environment
In nova.conf is set:
allow_migrate_to_same_host = True

but this is not enough. Resize in Dashboard returns:
Error: No valid host was found.

2017-12-08 14:35:36.127 18389 INFO nova.filters [req-21f0e039-f92a-
41d7-88c3-fbecd9b46c4b a719e1fa1583410e84a60584b057854f
76544321203c4ea5b40651daf4505f35 - - -] Filtering removed all hosts for
the request with instance ID 'cb76c5cc-3b0b-40eb-ba54-05b21331b693'.
Filter results: ['RetryFilter: (start: 1, end: 1)',
'AvailabilityZoneFilter: (start: 1, end: 0)']

It is not possible to specify:
scheduler_default_filters = AllHostsFilter
as this will ignore Availability zone specified per each instance launch.

Please advice if this is expected behavior and if can be fixed.

** Affects: nova
     Importance: Undecided
         Status: New

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

Title:
  Resize on same host in multiple-compute nodes environment not possible

Status in OpenStack Compute (nova):
  New

Bug description:
  Hi,

  On Ocata release, nova 15.0.7( Libvirt+KVM) its not possible to resize working instance on the same host, in multiple compute nodes environment
  In nova.conf is set:
  allow_migrate_to_same_host = True

  but this is not enough. Resize in Dashboard returns:
  Error: No valid host was found.

  2017-12-08 14:35:36.127 18389 INFO nova.filters [req-21f0e039-f92a-
  41d7-88c3-fbecd9b46c4b a719e1fa1583410e84a60584b057854f
  76544321203c4ea5b40651daf4505f35 - - -] Filtering removed all hosts
  for the request with instance ID 'cb76c5cc-3b0b-40eb-
  ba54-05b21331b693'. Filter results: ['RetryFilter: (start: 1, end:
  1)', 'AvailabilityZoneFilter: (start: 1, end: 0)']

  It is not possible to specify:
  scheduler_default_filters = AllHostsFilter
  as this will ignore Availability zone specified per each instance launch.

  Please advice if this is expected behavior and if can be fixed.

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


Follow ups