Cinder doesn't correctly handle None values in set quota

[Jamie Lennox]

Prior to openstackclient 1.1.0 when you did a quota set it would send None values to cinder for options it didn't want to change. Cinder would reject this change with a generic 400 bad client response.

There are two parts to this:

1. Cinder should return an appropriate error like it does when you try to set a non-integer value to a quota.
2. Should cinder ignore None values in a quota set?

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/180003

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/180003
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=f3630dd130d6e2e90b84416c9084e515604718ed
Submitter: Jenkins
Branch: master

commit f3630dd130d6e2e90b84416c9084e515604718ed
Author: Jamie Lennox <email address hidden>
Date: Tue May 5 11:50:21 2015 +1000

    Catch additional type conversion errors

    When converting strings to integers in quota we catch ValueError which
    will handle an input which is not a valid number, eg 'abc'. Extend this
    to covert TypeErrors which will handle things like a None value being
    passed.

    Partial-Bug: #1451637
    Change-Id: I7e3e694d539113beeb99001aeb80012ac4c1124d

[Sean McGinnis (sean-mcginnis)]

Automatically unassigning due to inactivity.