Description of problem: rbd_snap_list_end() segfaults if rbd_snap_list() fails Version-Release number of selected component (if applicable): 12.2.5 How reproducible: always Steps to Reproduce: 1. create an instance of `SnapIterator` using librbd's python binding in a very busy cluster, and rbd_snap_list() returns with ETIMEOUT 2. and `SnapIterator.__dealloc__()` gets called. Actual results: SIGSEGV is received. and the program crashes. Expected results: an exception is thrown. and the program does not crash. Additional info:
Manohar, see the first comment in this bz SnapIterator's constructor calls `rbd_snap_list()`, and its destructor calls rbd_snap_list_end(). i think what you need is to 1. # unplug the network cable or whatever way to cut down the connection between your testbed to cluster 2. snap_it = SnapIterator(image) 3 del snap_it
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:0475