Bug #49837
closed
mgr/pybind/snap_schedule: do not fail when no fs snapshots are available
Added by Sébastien Han about 3 years ago.
Updated almost 3 years ago.
Component(FS):
mgr/snap_schedule
Description
When calling the json output, we should not return any error but just an empty dict:
[root@rook-ceph-tools-78cdfd976c-xltx5 /]# ceph fs snap-schedule list / format=json
Error ENOENT: SnapSchedule for / not found
[root@rook-ceph-tools-78cdfd976c-xltx5 /]# echo $?
2
- Pull request ID set to 40157
- Project changed from mgr to CephFS
- Subject changed from snap_schedule: do not fail when no fs snapshots are available to mgr/pybind/snap_schedule: do not fail when no fs snapshots are available
- Status changed from New to Fix Under Review
- Target version set to v17.0.0
- Source set to Development
- Backport set to pacific,octopus
- Component(FS) mgr/snap_schedule added
- Assignee set to Sébastien Han
- Status changed from Fix Under Review to Pending Backport
- Copied to Backport #50538: pacific: mgr/pybind/snap_schedule: do not fail when no fs snapshots are available added
- Copied to Backport #50539: octopus: mgr/pybind/snap_schedule: do not fail when no fs snapshots are available added
@Patrick Donnelly - it seems that the snap_schedule module was added in Pacific, so I don't believe that this fix needs to be backported to Octopus. Can you just confirm so that I can close the Octopus backport tracker?
Cory Snyder wrote:
@Patrick Donnelly - it seems that the snap_schedule module was added in Pacific, so I don't believe that this fix needs to be backported to Octopus. Can you just confirm so that I can close the Octopus backport tracker?
It was going to be backported but got cancelled: https://github.com/ceph/ceph/pull/37142
I'll reject the OCtopus backport, thanks.
- Status changed from Pending Backport to Resolved
While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".
Also available in: Atom
PDF