| 2015-05-05 02:30:56 |
Jamie Lennox |
bug |
|
|
added bug |
| 2015-05-05 02:35:13 |
Jamie Lennox |
summary |
Calling quota set in 1.0 sends invalid messages to cinder |
Quota set sends invalid messages |
|
| 2015-05-05 02:46:02 |
Jamie Lennox |
description |
Calling:
# openstack --debug --os-identity-api-version=3 --os-user-domain-id default --os-project-domain-id default quota set --cores 4 demo
on OSC 1.0.3 results in a request that looks like:
'{"quota_set": {"gigabytes": null, "tenant_id": "9d33152f0d27406382b072806bbf66bf", "snapshots": null, "volumes": null}}'
There are two problems here:
1. Cinder cannot handle Null values for its values and returns a 400 which fails the command
2. OSC should not send this request to cinder if there are no cinder values present. This can be handled in another bug.
This was fixed in OSC 1.1.0 as a side effect of bug 1438377 where you can see the addition of the if value check, however this does not get backported into the stable 1.0 series. |
Calling:
# openstack --debug --os-identity-api-version=3 --os-user-domain-id default --os-project-domain-id default quota set --cores 4 demo
on OSC 1.0.3 results in a request that looks like:
'{"quota_set": {"gigabytes": null, "tenant_id": "9d33152f0d27406382b072806bbf66bf", "snapshots": null, "volumes": null}}'
There are two problems here:
1. Cinder cannot handle Null values for its values and returns a 400 which fails the command
2. OSC should not send this request to cinder if there are no cinder values present. This can be handled in another bug.
This was fixed in OSC 1.1.0 as a side effect of bug 1438377 where you can see the addition of the if value check, however this does not get backported into the stable 1.0 series. |
|
| 2015-05-05 02:46:52 |
Jamie Lennox |
tags |
|
kilo-backport-potential |
|
| 2015-05-05 02:49:30 |
Jamie Lennox |
description |
Calling:
# openstack --debug --os-identity-api-version=3 --os-user-domain-id default --os-project-domain-id default quota set --cores 4 demo
on OSC 1.0.3 results in a request that looks like:
'{"quota_set": {"gigabytes": null, "tenant_id": "9d33152f0d27406382b072806bbf66bf", "snapshots": null, "volumes": null}}'
There are two problems here:
1. Cinder cannot handle Null values for its values and returns a 400 which fails the command
2. OSC should not send this request to cinder if there are no cinder values present. This can be handled in another bug.
This was fixed in OSC 1.1.0 as a side effect of bug 1438377 where you can see the addition of the if value check, however this does not get backported into the stable 1.0 series. |
Calling:
# openstack --debug --os-identity-api-version=3 --os-user-domain-id default --os-project-domain-id default quota set --cores 4 demo
on OSC 1.0.3 results in a request that looks like:
'{"quota_set": {"gigabytes": null, "tenant_id": "9d33152f0d27406382b072806bbf66bf", "snapshots": null, "volumes": null}}'
There are two problems here:
1. Cinder cannot handle Null values for its values and returns a 400 which fails the command
2. OSC should not send this request to cinder if there are no cinder values present.
The problem is that we build the quota set requests using getattr(key, val, None) and do not check the return and so we create a full dictionary with None values for options we do not wish to change.
This was fixed for volume in OSC 1.1.0 as a side effect of bug 1438377 where you can see the addition of the if value check, however this does not get backported into the stable 1.0 series.
The problem still affects compute in master. |
|
| 2015-05-06 15:44:43 |
OpenStack Infra |
python-openstackclient: status |
New |
Fix Committed |
|
| 2015-05-08 02:12:00 |
Dean Troyer |
python-openstackclient: milestone |
|
m11 |
|
| 2015-05-27 22:07:53 |
Dean Troyer |
python-openstackclient: status |
Fix Committed |
Fix Released |
|
