disk 0 doesn't mean 0 disk, it means expand dynamically based on the
image. This sounds like a reasonable failure mode.
** Changed in: nova
Status: New => Invalid
--
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/1433994
Title:
Can't boot instance with fake_virt driver in flavor that has disk size
> 0
Status in OpenStack Compute (Nova):
Invalid
Bug description:
I set "VIRT_DRVER=fake" for my devstack.
And when I try to boot instance with flavor "m1.tiny" nova scheduler says
that I don't have disk space -
"ram:799488 disk:0 io_ops:0 instances:0 does not have 1024 MB usable disk, it
only has 0.0 MB usable disk."
It happens because scheduler calculates free_gb as minimum from
'compute.disk_available_least' and 'compute.free_disk_gb' if least is not None
but fake_virt driver defines 'disk_available_least = 0'.
Maybe this is not a bug about booting instance but maybe a bug about
list of flavors for fake_virt driver. (or friendly message that this
operation can not be proceeded).
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1433994/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
