no-vaild-host-found-due-to-nova-error-devstack

Bug #1502246 reported by Devdatta Kulkarni
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Solum
Invalid
High
Unassigned

Bug Description

Getting "No valid host found" error in devstack when deploying application DU.

Possible reason could be following error which is showing up in "nova-cpu" screen.

_available_resource from (pid=6039) run_periodic_tasks /usr/local/lib/python2.7/dist-packages/oslo_service/periodic_task.py:213
2015-10-02 17:13:00.035 ERROR nova.compute.manager [req-c72f8e91-e7ab-459e-988c-552d3603db61 None None] No compute node record for host devstack
2015-10-02 17:13:00.036 INFO nova.compute.resource_tracker [req-c72f8e91-e7ab-459e-988c-552d3603db61 None None] Auditing locally available compute resources for node devstack
2015-10-02 17:13:00.040 ERROR nova.compute.manager [req-c72f8e91-e7ab-459e-988c-552d3603db61 None None] Error updating resources for node devstack: Invalid input received: Missing keys: ['numa_topology']

Tags: solum-infra
Revision history for this message
Devdatta Kulkarni (devdatta-kulkarni) wrote :

On n-cond screen, seeing this stack trace:

2015-10-02 17:10:45.106 WARNING nova.scheduler.utils [req-bf920d82-5969-491a-b4c8-05f7af4a3623 demo demo] [instance: 5b24718e-be3d-4169-9e1e-198055300e5b] Setting instance to ERROR state.
2015-10-02 17:11:21.530 WARNING nova.scheduler.utils [req-e8f9166f-bee1-427e-af15-0b11523f3b92 demo demo] Failed to compute_task_build_instances: 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/nova/nova/scheduler/manager.py", line 84, in select_destinations
    filter_properties)

  File "/opt/stack/nova/nova/scheduler/filter_scheduler.py", line 90, in select_destinations
    raise exception.NoValidHost(reason=reason)

NoValidHost: No valid host was found. There are not enough hosts available.

2015-10-02 17:11:21.531 WARNING nova.scheduler.utils [req-e8f9166f-bee1-427e-af15-0b11523f3b92 demo demo] [instance: 4b8a6de9-a3bb-4e22-833e-bd6392d63c86] Setting instance to ERROR state.

Changed in solum:
importance: Undecided → High
summary: - no-vaild-host-found-due-to-nova-error
+ no-vaild-host-found-due-to-nova-error-devstack
tags: added: solum-infra
Revision history for this message
Devdatta Kulkarni (devdatta-kulkarni) wrote :

One approach to get around this issue is to use AllHostsFilter for Nova's scheduler_filter parameter.

The steps outlined here don't seem to lead to this issue.

https://github.com/devdattakulkarni/solum-provenance/blob/master/steps-to-enable-solum-with-devstack

So marking this as 'Invalid'.

Changed in solum:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.