Bug 2187661 - ceph fs snap-schedule listing is failing
Summary: ceph fs snap-schedule listing is failing
Keywords:
Status: CLOSED DUPLICATE of bug 2187659
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: CephFS
Version: 6.1
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 6.1
Assignee: Milind Changire
QA Contact: Hemanth Kumar
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-04-18 11:21 UTC by Hemanth Kumar
Modified: 2023-04-26 02:48 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-04-26 02:48:04 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHCEPH-6480 0 None None None 2023-04-18 11:22:51 UTC

Description Hemanth Kumar 2023-04-18 11:21:12 UTC
Created attachment 1957955 [details]
mgr_log

Description of problem:
--------------------------

When tried listing out the created snap-scheduled using "ceph fs snap-schedule list / --recursive", traceback is seen as follows.

[root@magna021 ~]# ceph fs snap-schedule list / --recursive
Error EINVAL: Traceback (most recent call last):
  File "/usr/share/ceph/mgr/mgr_module.py", line 1758, in _handle_command
    return CLICommand.COMMANDS[cmd['prefix']].call(self, cmd, inbuf)
  File "/usr/share/ceph/mgr/mgr_module.py", line 462, in call
    return self.func(mgr, **kwargs)
  File "/usr/share/ceph/mgr/snap_schedule/module.py", line 104, in snap_schedule_list
    abs_path = self.resolve_subvolume_path(use_fs, subvol, path)
NameError: name 'subvol' is not defined


Version-Release number of selected component (if applicable):
ceph version 17.2.6-22.el9cp

How reproducible:
Always


Expected : ceph fs snap-schedule list / --recursive - Should display all the snap-schedules created under /

Actual : Traceback is seen instead of displaying the snap-schedules created.


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