Open Stack

Hi Ramon,

The resize operation is successfully after I moved the two settings to the
[DEFAULT] section of the nova.conf at both the Controller and Compute
nodes.

Danny

On 9/13/14, 10:59 AM, "Ramon Acedo" <ramon at linux-labs.net> wrote:

>
>On 10 Sep 2014, at 19:44, Danny Choi (dannchoi) <dannchoi at cisco.com>
>wrote:
>
>> OpenStack version: Icehouse
>> 
>> Issue: fail to resize
>> 
>> Setup: 3 nodes, namely Controller, Compute and Network; with
>>nova-compute running solely on Compute node.
>> 
>> Steps to reproduce:
>>   1. Create an instance using image cirrus 0.3.2.
>>   2. Verify instance is running: nova list
>>   3. Resize the instance: nova resize cirrus 2 ‹poll
>>   4. Verify the resize: nova list
>>   5. Note that the server status is ACTIVE instead of VERIFY_RESIZE.
>>   6. Check nova-scheduler.log at Controller node and note the error.
>> 
>> Snippet of the nova-scheduler.log:
>> 
>> 2014-09-10 14:12:46.550 7488 WARNING nova.scheduler.utils
>>[req-63c12687-9f68-4501-a164-002c0f5fba7d
>>77bdd3f911744f72af7038d40d722439 73a095bf078443c9b340d871deaabcc3]
>>Failed to compute_task_migrate_server: No valid host was found.
>> Traceback (most recent call last):
>> 
>>   File "/usr/lib/python2.7/dist-packages/oslo/messaging/rpc/server.py",
>>line 139, in inner
>>     return func(*args, **kwargs)
>> 
>>   File "/usr/lib/python2.7/dist-packages/nova/scheduler/manager.py",
>>line 298, in select_destinations
>>     filter_properties)
>> 
>>   File 
>>"/usr/lib/python2.7/dist-packages/nova/scheduler/filter_scheduler.py",
>>line 140, in select_destinations
>>     raise exception.NoValidHost(reason='')
>> 
>> NoValidHost: No valid host was found.
>> 
>> 2014-09-10 14:12:46.552 7488 WARNING nova.scheduler.utils
>>[req-63c12687-9f68-4501-a164-002c0f5fba7d
>>77bdd3f911744f72af7038d40d722439 73a095bf078443c9b340d871deaabcc3]
>>[instance: 5960d4fe-8905-49f0-9cd9-1d09ded90810] Setting instance to
>>ACTIVE state.
>> 2014-09-10 14:12:46.645 7488 WARNING nova.conductor.manager
>>[req-63c12687-9f68-4501-a164-002c0f5fba7d
>>77bdd3f911744f72af7038d40d722439 73a095bf078443c9b340d871deaabcc3]
>>[instance: 5960d4fe-8905-49f0-9cd9-1d09ded90810] No valid host found for
>>cold migrate 
>> 
>> NOTE: I tried setting "allow_resize_to_same_host=true² and
>>³allow_migrate_to_same_host=true² in all nova.conf files and
>> restart nova services, but still saw the same issue.
>
>Could you double-check if the two settings are in the [DEFAULT] section
>of nova.conf?
>
>Ramon