'barbican secret list' returns index error on empty list
Bug #1547675 reported by
Christopher Solis
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-barbicanclient |
New
|
Undecided
|
Unassigned |
Bug Description
When running 'barbican secret list' on an empty database with a fresh installation of devstack, it is returning 'list index out of range'.
The same thing happens when using the openstack CLI as well.
christopher@
list index out of range
christopher@
list index out of range
Something must have been merged recently that is causing this because this was not previously returning this index error.
description: | updated |
Changed in python-barbicanclient: | |
assignee: | nobody → Ruchika (ruchika) |
Changed in python-barbicanclient: | |
assignee: | Ruchika (ruchika) → nobody |
Changed in python-barbicanclient: | |
assignee: | nobody → Kiran Totad (kiran-totad) |
Changed in python-barbicanclient: | |
assignee: | Kiran Totad (kiran-totad) → nobody |
status: | In Progress → New |
To post a comment you must log in.
As per our internal testing, the issue is introduced by cliff library version. If barbicanclient is using 1.16 or 1.17, then it happens. This has been fixed in 1.20 version (http:// docs.openstack. org/developer/ cliff/history. html#id1) which is released on 02/22/2016. It works fine with 1.15 version as well.
Looks like we need to exclude 1.16 and 1.17 version in global requirements in both stable/liberty and master branch to address it correctly. /github. com/openstack/ requirements/ blob/master/ global- requirements. txt#L20. /github. com/openstack/ requirements/ blob/stable/ liberty/ global- requirements. txt#L20
master - https:/
stable/liberty - https:/