Deleting a reserved snapshot is missing detach.start notificacion
Bug #1935011 reported by
Gorka Eguileor
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Fix Released
|
Medium
|
Gorka Eguileor |
Bug Description
When we delete an attachment that is in the reserved state Cinder only issues the detach.end notification without the corresponding detach.start notification.
Changed in cinder: | |
importance: | Undecided → Medium |
tags: | added: attachment notification volume |
Changed in cinder: | |
status: | New → In Progress |
To post a comment you must log in.
Reviewed: https:/ /review. opendev. org/c/openstack /cinder/ +/778534 /opendev. org/openstack/ cinder/ commit/ 68d49445778ef48 6e3ff656929405a b270a5a65d
Committed: https:/
Submitter: "Zuul (22348)"
Branch: master
commit 68d49445778ef48 6e3ff656929405a b270a5a65d
Author: Gorka Eguileor <email address hidden>
Date: Fri Jul 2 15:11:53 2021 +0200
Fix detach notification
Our current `attachment_delete` methods in the volume API and the
manager are using DB methods directly, which makes the OVOs present in
those methods get out of sync with the latest data, which leads to
notifications having the wrong data when we send them on volume detach.
This patch replaces DB method calls with OVO calls and moves the
notification call to the end of the method, where we have the final
status on the volume.
It also adds the missing detach.start notification when deleting an
attachment in the reserved state.
Closes-Bug: #1916980 e7716201dac00ed e8d57e6632f
Closes-Bug: #1935011
Change-Id: Ie48cf55deacd08