+++ This bug was initially created as a clone of Bug #1643419 +++
Description of problem:
It looks like our customer faced bug [1]. But I may be wrong here, so even if bug [1] is irrelevant, this issue should be investigated.
Steps to reproduce:
1. Create a flavor with Root Disk larger than the size of compute's HDD
2. Doublecheck if you cinder has a space needed to host a volume for new flavor
3. Start an instance, select to create cinder volume from image.
Expected result: instance is started, since its root disk has nothing to do with compute's storage.
Actual result:
2018-10-26 08:02:15.047 24 ERROR nova.conductor.manager
[req-65c6afc6-ee49-441c-adb1-23124f4cf28a b060f0bc09a74078820c46c934fe3c69 04d59562b2e5433eaa1465aca73cb06f - default default]
Failed to schedule instances: NoValidHost_Remote: No valid host was found.
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/server.py", line 226, in inner
return func(*args, **kwargs)
File "/usr/lib/python2.7/site-packages/nova/scheduler/manager.py", line 139, in select_destinations
raise exception.NoValidHost(reason="")
Workaround: to use a flavor with smaller root disk size and manually set a bigger one when creating an instance.
[1] https://bugs.launchpad.net/nova/+bug/1469179
--- Additional comment from Alex Stupnikov on 2018-10-26 04:22:10 EDT ---
I am not sure if this bug affects RHOSP 10, so will not create a duplicate for it. But I am sure that RHOSP 12 is affected, so will create a bug for it.