This seems to be fixed now!
# nova quota-update usage: nova quota-update [--instances <instances>] [--cores <cores>] [--ram <ram>] [--volumes <volumes>] [--gigabytes <gigabytes>] [--floating-ips <floating-ips>] [--fixed-ips <fixed-ips>] [--metadata-items <metadata-items>] [--injected-files <injected-files>] [--injected-file-content-bytes <injected-file-content-bytes>] [--injected-file-path-bytes <injected-file-path-bytes>] [--key-pairs <key-pairs>] [--security-groups <security-groups>] [--security-group-rules <security-group-rules>] [--force] <tenant-id>
# nova --version 2.13.0.33
This seems to be fixed now!
# nova quota-update
[-- ram <ram>] [--volumes <volumes>]
[-- gigabytes <gigabytes>]
[-- floating- ips <floating-ips>]
[-- fixed-ips <fixed-ips>]
[-- metadata- items <metadata-items>]
[-- injected- files <injected-files>]
[-- injected- file-content- bytes <injected- file-content- bytes>]
[-- injected- file-path- bytes <injected- file-path- bytes>]
[-- key-pairs <key-pairs>]
[-- security- groups <security-groups>]
[-- security- group-rules <security- group-rules> ]
[-- force]
<tenant- id>
usage: nova quota-update [--instances <instances>] [--cores <cores>]
# nova --version
2.13.0.33