| 2014-03-27 01:08:09 |
Matthew Edmonds |
bug |
|
|
added bug |
| 2014-03-27 01:27:19 |
Matt Riedemann |
tags |
|
api |
|
| 2014-03-27 01:33:20 |
Matthew Edmonds |
description |
HTTP 413 is supposed to mean (per RFC2616) that the request entity was too large. E.g., if you send an enormous body with the request. That is not at all how it is being used in the server resize request example below. The nova/api/openstack/compute/servers.py is coded to return 413 for QuotaError and PortLimitExceeded on create as well as for QuotaError on resize, and there may be other places 413 is being returned inappropriately.
POST https://9.5.126.113/powervc/openstack/compute/v2/6ce8fae0510349dcbf9b3965f7a20061/servers/8ebaabfc-9018-4ac1-afc6-630aee8a8ae3/action
Request body: { "resize": {
"flavor": {
"vcpus": 1,
"ram": 9999999999,
"disk": 20
}}}
Response: HTTP 413 (Request Entity Too Large)
Response body:
{
overLimit: {
message: "NV-02B1F9F Quota exceeded for ram: Requested 1410063359, but already used 6144 of 8000000 ram"
code: 413
retryAfter: "0"
}
-
} |
HTTP 413 is supposed to mean (per RFC2616) that the request entity was too large. E.g., if you send an enormous body with the request. That is not at all how it is being used in the server resize request example below. The nova/api/openstack/compute/servers.py is coded to return 413 for QuotaError and PortLimitExceeded on create as well as for QuotaError on resize, and there may be other places 413 is being returned inappropriately.
POST /v2/6ce8fae0510349dcbf9b3965f7a20061/servers/8ebaabfc-9018-4ac1-afc6-630aee8a8ae3/action
Request body: { "resize": {
"flavor": {
"vcpus": 1,
"ram": 9999999999,
"disk": 20
}}}
Response: HTTP 413 (Request Entity Too Large)
Response body:
{
overLimit: {
message: "NV-02B1F9F Quota exceeded for ram: Requested 1410063359, but already used 6144 of 8000000 ram"
code: 413
retryAfter: "0"
}
-
} |
|
| 2014-03-27 01:48:02 |
Matt Riedemann |
description |
HTTP 413 is supposed to mean (per RFC2616) that the request entity was too large. E.g., if you send an enormous body with the request. That is not at all how it is being used in the server resize request example below. The nova/api/openstack/compute/servers.py is coded to return 413 for QuotaError and PortLimitExceeded on create as well as for QuotaError on resize, and there may be other places 413 is being returned inappropriately.
POST /v2/6ce8fae0510349dcbf9b3965f7a20061/servers/8ebaabfc-9018-4ac1-afc6-630aee8a8ae3/action
Request body: { "resize": {
"flavor": {
"vcpus": 1,
"ram": 9999999999,
"disk": 20
}}}
Response: HTTP 413 (Request Entity Too Large)
Response body:
{
overLimit: {
message: "NV-02B1F9F Quota exceeded for ram: Requested 1410063359, but already used 6144 of 8000000 ram"
code: 413
retryAfter: "0"
}
-
} |
HTTP 413 is supposed to mean (per RFC2616) that the request entity was too large. E.g., if you send an enormous body with the request. That is not at all how it is being used in the server resize request example below. The nova/api/openstack/compute/servers.py is coded to return 413 for QuotaError and PortLimitExceeded on create as well as for QuotaError on resize, and there may be other places 413 is being returned inappropriately.
POST /v2/6ce8fae0510349dcbf9b3965f7a20061/servers/8ebaabfc-9018-4ac1-afc6-630aee8a8ae3/action
Request body: { "resize": {
"flavor": {
"vcpus": 1,
"ram": 9999999999,
"disk": 20
}}}
Response: HTTP 413 (Request Entity Too Large)
Response body:
{
overLimit: {
message: "Quota exceeded for ram: Requested 1410063359, but already used 6144 of 8000000 ram"
code: 413
retryAfter: "0"
}
-
} |
|
| 2014-03-31 18:25:54 |
Facundo Farias |
nova: assignee |
|
Facundo Farias (facundo-farias) |
|
| 2014-03-31 19:29:46 |
OpenStack Infra |
nova: status |
New |
In Progress |
|
| 2014-06-23 10:46:55 |
Christopher Yeoh |
nova: assignee |
Facundo Farias (facundo-farias) |
Christopher Yeoh (cyeoh-0) |
|
| 2014-07-25 07:41:44 |
OpenStack Infra |
nova: assignee |
Christopher Yeoh (cyeoh-0) |
zhu zhu (zhuzhubj) |
|
| 2014-07-25 10:07:06 |
Christopher Yeoh |
nova: assignee |
zhu zhu (zhuzhubj) |
Christopher Yeoh (cyeoh-0) |
|
| 2014-08-08 09:35:17 |
OpenStack Infra |
nova: assignee |
Christopher Yeoh (cyeoh-0) |
zhu zhu (zhuzhubj) |
|
| 2014-08-12 02:06:34 |
OpenStack Infra |
nova: status |
In Progress |
Fix Committed |
|
| 2014-08-27 15:24:57 |
zhu zhu |
nova: assignee |
zhu zhu (zhuzhubj) |
|
|
| 2014-09-05 10:01:42 |
Thierry Carrez |
nova: status |
Fix Committed |
Fix Released |
|
| 2014-09-05 10:01:42 |
Thierry Carrez |
nova: milestone |
|
juno-3 |
|
| 2014-10-16 08:52:13 |
Thierry Carrez |
nova: milestone |
juno-3 |
2014.2 |
|
