I’m administering an OpenStack cloud, running the Folsom release. One of the users requested some ephemeral disk space for their instances, so I created a custom flavour to meet their requirements. Unfortunately, all the instances went straight to the error state, because the scheduler couldn’t find a valid host. This was strange, because I knew there were several hosts with sufficient space. Here is the error message:
2013-06-12 13:20:19 DEBUG nova.scheduler.filter_scheduler [req-XXX] Attempting to build 1 instance(s) schedule_run_instance /usr/lib/pytho n2.6/site-packages/nova/scheduler/filter_scheduler.py:66 2013-06-12 13:20:19 WARNING nova.scheduler.manager [req-XXX] Failed to schedule_run_instance: No valid host was found. Exceeded max schedu ling attempts 3 for instance XXX 2013-06-12 13:20:19 WARNING nova.scheduler.manager [req-XXX] [instance: XXX] Setting instance to ERROR st ate.
After some searching, I came across this question on a Rackspace forum. The moderator suggested it was an Ubuntu packaging problem. It also exists in the Red Hat packages I’m using, so I made the change myself and it fixed the ephemeral disk creation errors I was seeing.
I’ll mention this to the Red Hat/Fedora developers.
A direct link to the diff is here.