yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #59931
[Bug 1636911] Re: Numa related exception didn't process by create server API
Reviewed: https://review.openstack.org/390919
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=d32d8c0ee1dbbdcc161bf6a7fcee3c5209be6e18
Submitter: Jenkins
Branch: master
commit d32d8c0ee1dbbdcc161bf6a7fcee3c5209be6e18
Author: Sergey Nikitin <snikitin@xxxxxxxxxxxx>
Date: Wed Oct 26 18:56:30 2016 +0300
Catch NUMA related exceptions in create server API method
The exceptions are raised by numa_get_constraints() method should be
caught by REST API layer explicitly. If we wouldn't catch them
nova will return responce with 500 status code instead of 400.
Following exceptions were caught:
* CPUThreadPolicyConfigurationInvalid
* ImageCPUPinningForbidden
* ImageCPUThreadPolicyForbidden
* MemoryPageSizeInvalid
* MemoryPageSizeForbidden
* RealtimeConfigurationInvalid
* RealtimeMaskNotFoundOrInvalid
Closes-Bug: #1636911
Closes-Bug: #1636688
Change-Id: I7c06bb2c3094eee403e615d6027c38502eaabd49
** 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/1636911
Title:
Numa related exception didn't process by create server API
Status in OpenStack Compute (nova):
Fix Released
Bug description:
Nova doesn't catches some set of exception in create server API
method. It causes responses with 500 (Internal Server Error) status
code instead of 400 (Bad Request) code.
These exceptions are:
* CPUThreadPolicyConfigurationInvalid
* ImageCPUPinningForbidden
* ImageCPUThreadPolicyForbidden
* MemoryPageSizeInvalid
* MemoryPageSizeForbidden
* RealtimeConfigurationInvalid
* RealtimeMaskNotFoundOrInvalid
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1636911/+subscriptions
References