Glance API v2 suffers from bug 1036193
Bug #1131705 reported by
Paul Bourke
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Glance |
Fix Released
|
High
|
Mark Washenberger | ||
Grizzly |
Fix Released
|
High
|
Mark Washenberger |
Bug Description
It seems glance-api v2 doesn't contain the fix for bug #1036193 and still uses the same ENGINE across workers. This can be demonstrated on devstack by the following crude script:
# Create 100 image entries
for i in $(seq 1 100); do
glance image-create
done
# <restart the server>
# Then run:
for i in $(seq 1 100); do
glance --os-image-
done
You'll get the errors outlined by David at https:/
Changed in glance: | |
milestone: | none → grizzly-rc1 |
status: | New → Confirmed |
importance: | Undecided → High |
Changed in glance: | |
assignee: | nobody → Mark Washenberger (markwash) |
tags: | added: grizzly-backport-potential |
tags: |
added: grizzly-r-potential removed: grizzly-backport-potential |
tags: |
added: grizzly-rc-potential removed: grizzly-r-potential |
Changed in glance: | |
milestone: | none → grizzly-rc2 |
To post a comment you must log in.
I have tested this on devstack with workers = 2, 4, 8 and have not been able to reproduce the problem. In addition, it appears the fix to bug #1036193 (namely https:/ /review. openstack. org/#/c/ 11612/) would affect everything that happens in the glance-api wsgi app, which covers both v1 and v2.
Can you help me understand why I'm not seeing this bug? I followed the instructions you posted.