Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
This project is now read‑only. Starting Monday, February 2, please use https://ibm-ceph.atlassian.net/ for all bug tracking management.

Bug 1488519

Summary: While renaming a non-existing rbd image returned segmentation fault
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Persona non grata <nobody+410372>
Component: RBDAssignee: Jason Dillaman <jdillama>
Status: CLOSED ERRATA QA Contact: Persona non grata <nobody+410372>
Severity: low Docs Contact:
Priority: medium    
Version: 3.0CC: ceph-eng-bugs, hnallurv
Target Milestone: rc   
Target Release: 3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ceph-12.2.1-1.el7cp Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-05 23:42:05 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
It contains the output of renaming a non-existing rbd image none

Description Persona non grata 2017-09-05 15:05:55 UTC
Created attachment 1322257 [details]
It contains the output of renaming a non-existing rbd image

Description of problem:
In Ubuntu with Ceph 3.0 ,renaming a non-existing rbd image returned segmentation fault.  

Version-Release number of selected component (if applicable):
Ceph 3.0

How reproducible:
Always

Actual results:
Actual result attached in the file.

Expected results:
Error message stating non-existence of rbd image.

Comment 2 Jason Dillaman 2017-09-05 16:13:31 UTC
Upstream PR: https://github.com/ceph/ceph/pull/17502

Comment 6 errata-xmlrpc 2017-12-05 23:42:05 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/RHBA-2017:3387