yahoo-eng-team team mailing list archive

[Thierry Carrez <thierry.carrez+lp@xxxxxxxxx>]

** Changed in: nova
       Status: Fix Committed => Fix Released

** Changed in: nova
    Milestone: None => juno-3

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

Title:
  It returned RESP:202 even if NoValidHost exception raised when run
  nova resize

Status in OpenStack Compute (Nova):
  Fix Released

Bug description:
  When I run "nova --debug resize instanceid flavorid", nova scheduler will raise NoValidHost exception If there is no enough resource available on any computer node for the flavor requested. Then nova conductor will catch the exception and report Warning messages as follows:
  WARNING nova.scheduler.utils [req-c0d5f130-c5a9-41b7-8fe4-4d08be4cc774 9ed1534f040c43e98293f6bc6b632e96 bd5848810607480d968b6d1ca9a36637] Failed to compute_task_migrate_server: No valid host was found.

  However, nova api does not catch exception but response 202. I think
  this is bug that nova resize failed but return 202 which is Normal
  Response Code.

  By the way, one question is why "CoreFilter" isn't default in "scheduler_default_filters"?  That cause scheduler do not check the vcpu resource when run nova resize.
  cfg.ListOpt('scheduler_default_filters',
                  default=[
                    'RetryFilter',
                    'AvailabilityZoneFilter',
                    'RamFilter',
                    'ComputeFilter',
                    'ComputeCapabilitiesFilter',
                    'ImagePropertiesFilter'
                    ],

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