Reviewed: https://review.opendev.org/729967 Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=f76d09b19d5b7530b7e4e9fc255835f6aff5db6a Submitter: Zuul Branch: master
commit f76d09b19d5b7530b7e4e9fc255835f6aff5db6a Author: Stephen Finucane <[email protected]> Date: Thu May 21 14:43:25 2020 +0100 hardware: Raise useful error for invalid mempage size The 'hw:mem_page_size' extra spec allows you to specify values in three ways: via a relative size alias (large, small, any), via exact byte values, and via an SI/IEC/mixed representation (e.g. 2MB, 1GB). Currently, attempting to use an invalid variant of the latter, such as '2M', will raise a rather confusing error message: Invalid memory page size '0' Correct this so we instead see something like so: Invalid memory page size '2M' Change-Id: I3af99f03514904da09f7b71f430b43bf75e8be67 Signed-off-by: Stephen Finucane <[email protected]> Closes-Bug: #1879964 ** Changed in: nova Status: In Progress => Fix Released -- 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/1879964 Title: Invalid value for 'hw:mem_page_size' raises confusing error Status in OpenStack Compute (nova): Fix Released Bug description: Configure a flavor like so: openstack flavor create hugepage --ram 1024 --disk 10 --vcpus 1 test openstack flavor set hugepage --property hw:mem_page_size=2M test Attempt to boot an instance. It will fail with the following error message: Invalid memory page size '0' (HTTP 400) (Request-ID: req- 338bf619-3a54-45c5-9c59-ad8c1d425e91) You wouldn't know from reading it, but this is because the property should read 'hw:mem_page_size=2MB' (note the extra 'B'). To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1879964/+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
