Incorrect status change after image uploading in v2
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Glance |
In Progress
|
High
|
Darja Shakhray | ||
Juno |
Fix Released
|
High
|
Unassigned | ||
Kilo |
Fix Released
|
High
|
Unassigned |
Bug Description
If the image is deleted (i.e. its status changed to 'deleted' in db) when it's uploading through image-upload command in v2, its status surprisingly switches from 'deleted' to 'active' without any exception.
There is the code that should handle NotFound exception in that case
https:/
except exception.NotFound as e:
msg = (_("Image %(id)s could not be found after upload."
"The image may have been deleted during the upload: "
"%(error)s Cleaning up the chunks uploaded") %
{'id': image_id,
'error': utils.exception
but it never executes because the exception is not raised.
In v1 this problem is solved with explicitly passing from_state argument, but in v2 it's not possible.
Changed in glance: | |
status: | New → Confirmed |
description: | updated |
Changed in glance: | |
assignee: | nobody → Mike Fedosin (mfedosin) |
Changed in glance: | |
importance: | Undecided → High |
tags: | added: juno-rc1-potential |
Changed in glance: | |
status: | Confirmed → In Progress |
tags: |
added: juno-rc-potential removed: juno-rc1-potential |
tags: |
added: juno-backport-potential removed: juno-rc-potential |
tags: | added: kilo-1 |
Changed in glance: | |
milestone: | none → kilo-2 |
tags: | removed: kilo-1 |
Changed in glance: | |
milestone: | kilo-2 → kilo-3 |
Changed in glance: | |
milestone: | kilo-3 → kilo-rc1 |
tags: | added: kilo-rc-potential |
Changed in glance: | |
milestone: | kilo-rc1 → none |
tags: | removed: kilo-rc-potential |
Changed in glance: | |
assignee: | nobody → Darja Shakhray (dshakhray) |
Changed in glance: | |
status: | Invalid → In Progress |
https:/ /review. openstack. org/#/c/ 123799/ 9