Bug #12176
librbd/internal.cc: 1967: FAILED assert(watchers.size() == 1)
0%
Related issues
Associated revisions
librbd: assertion failure race condition if watch disconnected
It's possible for librbd's watch of the header object to be reset by
connection issues just prior to the image being removed. This will
causes an assertion failure which assumes at least one watcher on the
image.
Fixes: #12176
Backport: hammer, firefly
Signed-off-by: Jason Dillaman <dillaman@redhat.com>
librbd: assertion failure race condition if watch disconnected
It's possible for librbd's watch of the header object to be reset by
connection issues just prior to the image being removed. This will
causes an assertion failure which assumes at least one watcher on the
image.
Fixes: #12176
Backport: hammer, firefly
Signed-off-by: Jason Dillaman <dillaman@redhat.com>
(cherry picked from commit af276de4f299960e43761904c043924cec5fef11)
librbd: assertion failure race condition if watch disconnected
It's possible for librbd's watch of the header object to be reset by
connection issues just prior to the image being removed. This will
causes an assertion failure which assumes at least one watcher on the
image.
Fixes: #12176
Backport: hammer, firefly
Signed-off-by: Jason Dillaman <dillaman@redhat.com>
(cherry picked from commit af276de4f299960e43761904c043924cec5fef11)
History
#1 Updated by Jason Dillaman almost 9 years ago
- Backport set to hammer,firefly
librados bubbled up the following error:
librbd::ImageWatcher: 0x3bffcc0 image watch failed: 63381088, (110) Connection timed out
#2 Updated by Jason Dillaman almost 9 years ago
- Status changed from In Progress to Fix Under Review
#3 Updated by Jason Dillaman almost 9 years ago
- Status changed from Fix Under Review to Pending Backport
#4 Updated by Nathan Cutler over 8 years ago
- Status changed from Pending Backport to Resolved