Public bug reported:
The value of disk_available_least become negative unexpectedly, because we
allow to boot a image-based vm using a flavor with 0 GB disk size.
When user try to boot a image-based vm using a flavor with 0 GB disk size, Nova
use the virtual size from image property to replace the '0' size to create disk
file in instance folder.
This virtual size from image property make the value of disk_available_least
inconsistent with flavor-based estimate. It makes user confused sometimes.
Maybe we should forbid the creation of a vm from a flavor with zero disk size,
and throw out a HTTP exception in Nova API.
** Affects: nova
Importance: Undecided
Status: New
--
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/1758278
Title:
disk_available_least become a negative value unexpectedly
Status in OpenStack Compute (nova):
New
Bug description:
The value of disk_available_least become negative unexpectedly, because we
allow to boot a image-based vm using a flavor with 0 GB disk size.
When user try to boot a image-based vm using a flavor with 0 GB disk size,
Nova use the virtual size from image property to replace the '0' size to create
disk file in instance folder.
This virtual size from image property make the value of disk_available_least
inconsistent with flavor-based estimate. It makes user confused sometimes.
Maybe we should forbid the creation of a vm from a flavor with zero disk
size, and throw out a HTTP exception in Nova API.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1758278/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
