yahoo-eng-team team mailing list archive

[Danny Choi <dannchoi@xxxxxxxxx>]

Public bug reported:

OpenStack version: Icehouse

Issue: fail to resize VM

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-conductor.log at Controller node and note the error.

Snippet of the nova-conductor.log:

2014-09-12 10:10:22.923 1290 WARNING nova.scheduler.utils [req-c7b0a97d-7c79-477b-ab97-48e55e956bdc 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-12 10:10:22.924 1290 WARNING nova.scheduler.utils [req-c7b0a97d-7c79-477b-ab97-48e55e956bdc 77bdd3f911744f72af7038d40d722439 73a095bf078443c9b340d871deaabcc3] [instance: 569de892-5f5a-48f1-ac5e-a88e9d9b4c94] Setting instance to ACTIVE state.
2014-09-12 10:10:22.973 1290 WARNING nova.conductor.manager [req-c7b0a97d-7c79-477b-ab97-48e55e956bdc 77bdd3f911744f72af7038d40d722439 73a095bf078443c9b340d871deaabcc3] [instance: 569de892-5f5a-48f1-ac5e-a88e9d9b4c94] No valid host found for cold migrate 

root@Controller:/home/guest# nova list
+--------------------------------------+--------+--------+------------+-------------+---------------------+
| ID                                   | Name   | Status | Task State | Power State | Networks            |
+--------------------------------------+--------+--------+------------+-------------+---------------------+
| 569de892-5f5a-48f1-ac5e-a88e9d9b4c94 | cirros | ACTIVE | -          | Running     | int-net=172.16.1.67 |
+--------------------------------------+--------+--------+------------+-------------+---------------------+
root@Controller:/home/guest# nova resize cirros 2 --poll
Server resizing... 100% complete
Finished
root@Controller:/home/guest# nova list
+--------------------------------------+--------+--------+------------+-------------+---------------------+
| ID                                   | Name   | Status | Task State | Power State | Networks            |
+--------------------------------------+--------+--------+------------+-------------+---------------------+
| 569de892-5f5a-48f1-ac5e-a88e9d9b4c94 | cirros | ACTIVE | -          | Running     | int-net=172.16.1.67 |
+--------------------------------------+--------+--------+------------+-------------+---------------------+


NOTE: I tried setting "allow_resize_to_same_host=true” and “allow_migrate_to_same_host=true” in nova.conf at both the controller and compute node and restart nova services, but still saw the same issue.

** 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/1368789

Title:
  Fail to resize VM; No valid host was found

Status in OpenStack Compute (Nova):
  New

Bug description:
  OpenStack version: Icehouse

  Issue: fail to resize VM

  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-conductor.log at Controller node and note the error.

  Snippet of the nova-conductor.log:

  2014-09-12 10:10:22.923 1290 WARNING nova.scheduler.utils [req-c7b0a97d-7c79-477b-ab97-48e55e956bdc 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-12 10:10:22.924 1290 WARNING nova.scheduler.utils [req-c7b0a97d-7c79-477b-ab97-48e55e956bdc 77bdd3f911744f72af7038d40d722439 73a095bf078443c9b340d871deaabcc3] [instance: 569de892-5f5a-48f1-ac5e-a88e9d9b4c94] Setting instance to ACTIVE state.
  2014-09-12 10:10:22.973 1290 WARNING nova.conductor.manager [req-c7b0a97d-7c79-477b-ab97-48e55e956bdc 77bdd3f911744f72af7038d40d722439 73a095bf078443c9b340d871deaabcc3] [instance: 569de892-5f5a-48f1-ac5e-a88e9d9b4c94] No valid host found for cold migrate 

  root@Controller:/home/guest# nova list
  +--------------------------------------+--------+--------+------------+-------------+---------------------+
  | ID                                   | Name   | Status | Task State | Power State | Networks            |
  +--------------------------------------+--------+--------+------------+-------------+---------------------+
  | 569de892-5f5a-48f1-ac5e-a88e9d9b4c94 | cirros | ACTIVE | -          | Running     | int-net=172.16.1.67 |
  +--------------------------------------+--------+--------+------------+-------------+---------------------+
  root@Controller:/home/guest# nova resize cirros 2 --poll
  Server resizing... 100% complete
  Finished
  root@Controller:/home/guest# nova list
  +--------------------------------------+--------+--------+------------+-------------+---------------------+
  | ID                                   | Name   | Status | Task State | Power State | Networks            |
  +--------------------------------------+--------+--------+------------+-------------+---------------------+
  | 569de892-5f5a-48f1-ac5e-a88e9d9b4c94 | cirros | ACTIVE | -          | Running     | int-net=172.16.1.67 |
  +--------------------------------------+--------+--------+------------+-------------+---------------------+

  
  NOTE: I tried setting "allow_resize_to_same_host=true” and “allow_migrate_to_same_host=true” in nova.conf at both the controller and compute node and restart nova services, but still saw the same issue.

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