rbd cannot delete residual image from ceph in some situations
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mirantis OpenStack |
Fix Released
|
Medium
|
MOS Glance | ||
6.1.x |
Won't Fix
|
Medium
|
MOS Maintenance | ||
7.0.x |
Fix Released
|
Medium
|
Sergii Rizvan | ||
8.0.x |
Fix Released
|
Medium
|
Sergii Rizvan | ||
9.x |
Fix Released
|
Medium
|
MOS Glance |
Bug Description
Upstream bug: https:/
Description:
When user through glance RESTful api upload image, the image generally has a large size.
In fact, uploading a large enough image may be failed due to http connection broken or other situations like that.
RBD supports a mechanism that when add operation failed, rollback operation must be triggered (delete residual image if it was created).
Base on a condition, we have already encountered, that the incomplete image has not been taken snapshot yet, then rollback operation do unprotect snap will throw exception "rbd.ImageNotFo
This exception will be disposed finally, while the code relating to remove residual image from ceph has been skipped.
Therefore, re-uploading image will failed using the same image id due to above reason (residual image already exists) & residual image need to be deleted manually from ceph.
tags: | added: customer-found |
tags: | added: ct2 |
tags: | added: on-verification |
tags: | added: on-automation |
tags: | added: on-verification |
(This check performed automatically)
Please, make sure that bug description contains the following sections filled in with the appropriate data related to the bug you are describing:
actual result
version
expected result
steps to reproduce
For more detailed information on the contents of each of the listed sections see https:/ /wiki.openstack .org/wiki/ Fuel/How_ to_contribute# Here_is_ how_you_ file_a_ bug