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 1362055

Summary:	2.0: "rbd du <non existing image>" does not print an error message
Product:	[Red Hat Storage] Red Hat Ceph Storage	Reporter:	Harish NV Rao <hnallurv>
Component:	RBD	Assignee:	Jason Dillaman <jdillama>
Status:	CLOSED ERRATA	QA Contact:	Tejas <tchandra>
Severity:	medium	Docs Contact:
Priority:	low
Version:	2.0	CC:	bniver, ceph-eng-bugs, flucifre, kdreyer
Target Milestone:	rc
Target Release:	3.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	RHEL: ceph-12.1.2-1.el7cp Ubuntu: ceph_12.1.2-2redhat1xenial	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-12-05 23:31:14 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:

Description Harish NV Rao 2016-08-01 09:18:18 UTC

Description of problem:

"rbd du <non existing image>" does not print an error message

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


How reproducible: always


Steps to Reproduce:
1. execute "rbd du <non existing image>"

Actual results:
prints:
NAME PROVISIONED USED 

Expected results:
An error message indicating invalid image name

Additional info:

Comment 2 Jason Dillaman 2017-01-04 21:24:26 UTC

Fix is included in Ceph v10.2.6

Comment 5 Tejas 2017-08-30 12:15:49 UTC

 rbd du p2/i1
specified image i1 is not found.
du failed: (2) No such file or directory

rbd du p2/im1
NAME PROVISIONED  USED 
im1       20480M 4196M 


ceph -v
ceph version 12.1.4-1.el7cp (b661348f156f148d764b998b65b90451f096cb27) luminous (rc)

Moving to Verified.

Comment 8 errata-xmlrpc 2017-12-05 23:31:14 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