Comment 2 for bug 1263691

I was not able to reproduce this problem.

If I stop the scheduler, create a volume, start the scheduler...it'll eventually pick up the message and hand it off to a cinder-volume host to be created and set to available.

If I stop the cinder-volume service, create a volume, the scheduler will just error out that it couldn't find a suitable host and set the status to error.