Bugzilla (bugzilla.redhat.com) will be under maintenance for infrastructure upgrades and will not be available on July 31st between 12:30 AM - 05:30 AM UTC. We appreciate your understanding and patience. You can follow status.redhat.com for details.
Bug 1655685 - rbd_snap_list_end() segfaults if rbd_snap_list() fails
Summary: rbd_snap_list_end() segfaults if rbd_snap_list() fails
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat
Component: RBD
Version: 2.5
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: z4
: 2.5
Assignee: Jason Dillaman
QA Contact: Manohar Murthy
Aron Gunn
URL:
Whiteboard:
Depends On: 1655681
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-12-03 17:03 UTC by Jason Dillaman
Modified: 2019-04-11 13:33 UTC (History)
7 users (show)

Fixed In Version: RHEL: ceph-10.2.10-47.el7cp Ubuntu: ceph_10.2.10-41redhat1
Doc Type: Bug Fix
Doc Text:
.The _python-rbd_ _list_snaps()_ method no longer segfaults after an error This issue was discovered with OpenStack Cinder Backup when `rados_connect_timeout` was set. Normally the timeout is not enabled. If the cluster was highly loaded the timeout could be reached, causing the segfault. With this update to {product}, if the timeout is reached a segfault no longer occurs.
Clone Of: 1655681
Environment:
Last Closed: 2019-04-11 13:32:56 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Ceph Project Bug Tracker 37508 0 None None None 2018-12-03 17:03:28 UTC
Red Hat Product Errata RHSA-2019:0747 0 None None None 2019-04-11 13:33:08 UTC

Comment 9 errata-xmlrpc 2019-04-11 13:32:56 UTC
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/RHSA-2019:0747


Note You need to log in before you can comment on or make changes to this bug.