Bug 2004909 - rbd mirror snapshot schedule rm returns 0 when tried to remove non-existent schedule
Summary: rbd mirror snapshot schedule rm returns 0 when tried to remove non-existent s...
Keywords:
Status: ASSIGNED
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: RBD-Mirror
Version: 5.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: 7.0
Assignee: Christopher Hoffman
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-09-16 12:09 UTC by Vasishta
Modified: 2023-07-31 21:50 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Ceph Project Bug Tracker 54999 0 None None None 2022-03-22 19:06:52 UTC
Red Hat Issue Tracker RHCEPH-1804 0 None None None 2021-09-18 18:54:25 UTC

Description Vasishta 2021-09-16 12:09:16 UTC
Description of problem:
rbd mirror snapshot schedule rm returns 0 when tried to remove non-existent schedule

this decreases usability, if a user makes any typo in his command, he wouldn't get to know that there has been some mishap and he wouldn't be achieving what exactly he wished to achieve.

Version-Release number of selected component (if applicable):
16.2.0-117.el8cp

How reproducible:
Always

Steps to Reproduce:
1. Create two clusters with rbd snapshot based mirroring enabled
2. Try to delete non-existent schedule

Actual results:
[ceph: root@magna008 /]# rbd mirror snapshot schedule ls -p two_way --recursive
POOL     NAMESPACE  IMAGE  SCHEDULE          
two_way  -          -      every 1h, every 6h
[ceph: root@magna008 /]# rbd mirror snapshot schedule rm  --pool two_way --image image 7h
[ceph: root@magna008 /]# echo $?
0


Expected results:
Error message should be displayed if user tries to delete non existent schedule

Additional info:


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