yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #33549
[Bug 1463200] [NEW] check-tempest-dsvm-multinode-full fails due to "Failed to compute_task_migrate_server: No valid host was found"
Public bug reported:
http://logs.openstack.org/81/181781/3/check/check-tempest-dsvm-
multinode-full/e13a3a8/logs/screen-n-cond.txt.gz?level=TRACE
2015-06-08 20:37:00.205 WARNING nova.scheduler.utils [req-73a672be-7fe7-4bb4-a13c-6c1bbe6eb3d6 ServerDiskConfigTestJSON-326631053 ServerDiskConfigTestJSON-280407802] Failed to compute_task_migrate_server: No valid host was found. There are not enough hosts available.
Traceback (most recent call last):
File "/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/server.py", line 142, in inner
return func(*args, **kwargs)
File "/opt/stack/new/nova/nova/scheduler/manager.py", line 86, in select_destinations
filter_properties)
File "/opt/stack/new/nova/nova/scheduler/filter_scheduler.py", line 89, in select_destinations
raise exception.NoValidHost(reason=reason)
NoValidHost: No valid host was found. There are not enough hosts
available.
http://logstash.openstack.org/#eyJzZWFyY2giOiJtZXNzYWdlOlwiRmFpbGVkIHRvIGNvbXB1dGVfdGFza19taWdyYXRlX3NlcnZlcjogTm8gdmFsaWQgaG9zdCB3YXMgZm91bmRcIiBBTkQgdGFnczpcInNjcmVlbi1uLWNvbmQudHh0XCIiLCJmaWVsZHMiOltdLCJvZmZzZXQiOjAsInRpbWVmcmFtZSI6IjYwNDgwMCIsImdyYXBobW9kZSI6ImNvdW50IiwidGltZSI6eyJ1c2VyX2ludGVydmFsIjowfSwic3RhbXAiOjE0MzM4MDMzMjU1ODN9
There really isn't much in the compute logs for errors except this:
http://logs.openstack.org/81/181781/3/check/check-tempest-dsvm-
multinode-
full/e13a3a8/logs/screen-n-cpu.txt.gz?level=TRACE#_2015-06-08_20_24_45_822
2015-06-08 20:24:45.822 ERROR nova.compute.manager [req-5e3903be-
18a7-4aa4-b874-f7116bac6e43 None None] No compute node record for host
devstack-trusty-2-node-rax-iad-2929470.slave.openstack.org
But that's not even at the same time.
I see this in the n-api logs around the same time as the failures:
http://logs.openstack.org/81/181781/3/check/check-tempest-dsvm-
multinode-
full/e13a3a8/logs/screen-n-api.txt.gz?level=TRACE#_2015-06-08_20_35_01_485
015-06-08 20:35:01.485 WARNING nova.compute.api [req-eec9e9fb-8794-47cc-
a67a-f60b3dd85ab4 MigrationsAdminTest-1879224794
MigrationsAdminTest-93634600] [instance: 24d02424-1af8-43b8-941c-
507806a22e79] instance's host devstack-trusty-2-node-rax-
iad-2929470.slave.openstack.org is down, deleting from database
** 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/1463200
Title:
check-tempest-dsvm-multinode-full fails due to "Failed to
compute_task_migrate_server: No valid host was found"
Status in OpenStack Compute (Nova):
New
Bug description:
http://logs.openstack.org/81/181781/3/check/check-tempest-dsvm-
multinode-full/e13a3a8/logs/screen-n-cond.txt.gz?level=TRACE
2015-06-08 20:37:00.205 WARNING nova.scheduler.utils [req-73a672be-7fe7-4bb4-a13c-6c1bbe6eb3d6 ServerDiskConfigTestJSON-326631053 ServerDiskConfigTestJSON-280407802] Failed to compute_task_migrate_server: No valid host was found. There are not enough hosts available.
Traceback (most recent call last):
File "/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/server.py", line 142, in inner
return func(*args, **kwargs)
File "/opt/stack/new/nova/nova/scheduler/manager.py", line 86, in select_destinations
filter_properties)
File "/opt/stack/new/nova/nova/scheduler/filter_scheduler.py", line 89, in select_destinations
raise exception.NoValidHost(reason=reason)
NoValidHost: No valid host was found. There are not enough hosts
available.
http://logstash.openstack.org/#eyJzZWFyY2giOiJtZXNzYWdlOlwiRmFpbGVkIHRvIGNvbXB1dGVfdGFza19taWdyYXRlX3NlcnZlcjogTm8gdmFsaWQgaG9zdCB3YXMgZm91bmRcIiBBTkQgdGFnczpcInNjcmVlbi1uLWNvbmQudHh0XCIiLCJmaWVsZHMiOltdLCJvZmZzZXQiOjAsInRpbWVmcmFtZSI6IjYwNDgwMCIsImdyYXBobW9kZSI6ImNvdW50IiwidGltZSI6eyJ1c2VyX2ludGVydmFsIjowfSwic3RhbXAiOjE0MzM4MDMzMjU1ODN9
There really isn't much in the compute logs for errors except this:
http://logs.openstack.org/81/181781/3/check/check-tempest-dsvm-
multinode-
full/e13a3a8/logs/screen-n-cpu.txt.gz?level=TRACE#_2015-06-08_20_24_45_822
2015-06-08 20:24:45.822 ERROR nova.compute.manager [req-5e3903be-
18a7-4aa4-b874-f7116bac6e43 None None] No compute node record for host
devstack-trusty-2-node-rax-iad-2929470.slave.openstack.org
But that's not even at the same time.
I see this in the n-api logs around the same time as the failures:
http://logs.openstack.org/81/181781/3/check/check-tempest-dsvm-
multinode-
full/e13a3a8/logs/screen-n-api.txt.gz?level=TRACE#_2015-06-08_20_35_01_485
015-06-08 20:35:01.485 WARNING nova.compute.api [req-eec9e9fb-8794
-47cc-a67a-f60b3dd85ab4 MigrationsAdminTest-1879224794
MigrationsAdminTest-93634600] [instance: 24d02424-1af8-43b8-941c-
507806a22e79] instance's host devstack-trusty-2-node-rax-
iad-2929470.slave.openstack.org is down, deleting from database
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1463200/+subscriptions
Follow ups
References