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 Jira Cloud for all bug tracking management.

Bug 1357001

Summary: [rbd-cli] - No error message when tried to delete a meta key that doesn't exists
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Vasishta <vashastr>
Component: RBDAssignee: Jason Dillaman <jdillama>
Status: CLOSED ERRATA QA Contact: Madhavi Kasturi <mkasturi>
Severity: medium Docs Contact:
Priority: low    
Version: 2.0CC: anharris, ceph-eng-bugs, flucifre, hnallurv, kdreyer, tserlin
Target Milestone: rc   
Target Release: 4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ceph-14.2.0 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-01-31 12:44:52 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 Vasishta 2016-07-15 13:05:24 UTC 
Description of problem:
While trying to delete image-meta key that doesn't exist, there is no error message getting displayed.


Version-Release number of selected component (if applicable):
ceph version 10.2.2-15.el7cp

How reproducible:
Always

Steps to Reproduce:
1. Try to delete a image-meta key that doesn't exist
( sudo rbd image-meta remove <image-spec> random_key )

# rbd image-meta get test_rbd/test_image06 random_key
failed to get metadata random_key of image : (2) No such file or directory
rbd: getting metadata failed: (2) No such file or directory

# rbd image-meta remove test_rbd/test_image06 random_key

============================================================

Actual results:
command exits without any message.

Expected results:
there should be an error message displayed
Comment 2 Giridhar Ramaraju 2019-08-05 13:10:33 UTC 
Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. 

Regards,
Giri
Comment 3 Giridhar Ramaraju 2019-08-05 13:11:36 UTC 
Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. 

Regards,
Giri
Comment 6 errata-xmlrpc 2020-01-31 12:44:52 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-2020:0312