"get console output" v3 API should allow -1 as the length
Bug #1295426 reported by
Ken'ichi Ohmichi
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Undecided
|
Ken'ichi Ohmichi | ||
python-novaclient |
Fix Released
|
Undecided
|
Ken'ichi Ohmichi |
Bug Description
If running "nova console-log" command against v3 API, the command fails like the following:
$ nova --os-compute-
ERROR: Invalid input for field/attribute length. Value: None. None is not of type 'integer', 'string' (HTTP 400) (Request-ID: req-b8588c9b-
$
This is because API schema of the API does not allow null as the length of log. The other APIs(quota, etc) considers -1 as an unlimited value.
So it would be nice that "get console output" API also considers -1 as the
unlimited length for API consistency.
Changed in nova: | |
assignee: | nobody → Ken'ichi Ohmichi (oomichi) |
affects: | nova → python-novaclient |
affects: | python-novaclient → nova |
Changed in nova: | |
status: | In Progress → Fix Committed |
Changed in python-novaclient: | |
assignee: | nobody → Ken'ichi Ohmichi (oomichi) |
summary: |
- "get console output" v3 API should allow "null" as the length + "get console output" v3 API should allow -1 as the length |
description: | updated |
Changed in nova: | |
milestone: | none → juno-1 |
status: | Fix Committed → Fix Released |
Changed in python-novaclient: | |
milestone: | none → 2.18.0 |
Changed in python-novaclient: | |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | juno-1 → 2014.2 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/81947
Review: https:/