Bug #58095
closed
snap-schedule: handle non-existent path gracefully during snapshot creation
Added by Milind Changire over 1 year ago.
Updated 9 months ago.
Category:
Administration/Usability
Backport:
reef,quincy,pacific
Component(FS):
mgr/snap_schedule
Description
The most common mistake that users tend to do is include the mount point path along with the file-system path when using snap-schedule commands.
This leads to the snap-schedule module encountering invalid paths as far as the file-system is concerned.
- ceph-qa-suite fs added
- Component(FS) mgr/snap_schedule added
- Labels (FS) task(easy) added
- Assignee set to Milind Changire
Milind Changire wrote:
The most common mistake that users tend to do is include the mount point path along with the file-system path when using snap-schedule commands.
Doesn't our documentation mention this clearly? If not, we should fix the doc.
This leads to the snap-schedule module encountering invalid paths as far as the file-system is concerned.
This was discussed as part of design with Jan - users can add schedules to non-existent file system paths, which may be created at a later point in time. Additionally, if the number of consecutive failures hit a certain configured value, the schedule would be deactivated for the path. Are you not seeing that?
Venky Shankar wrote:
Milind Changire wrote:
The most common mistake that users tend to do is include the mount point path along with the file-system path when using snap-schedule commands.
Doesn't our documentation mention this clearly? If not, we should fix the doc.
I'll look at the docs and put in a note there.
This leads to the snap-schedule module encountering invalid paths as far as the file-system is concerned.
This was discussed as part of design with Jan - users can add schedules to non-existent file system paths, which may be created at a later point in time. Additionally, if the number of consecutive failures hit a certain configured value, the schedule would be deactivated for the path. Are you not seeing that?
The schedule deactivation part is there, but there's no track kept of number of consecutive failures. The moment an exception get raised during snapshot creation, due to file-system or db updates, the schedule is set to inactive.
- Subject changed from snap-schedule: validate path for all commands to snap-schedule: handle non-existent path gracefully during snapshot creation
- Category set to Administration/Usability
- Target version set to v18.0.0
- Backport set to pacific,quincy
- Pull request ID set to 49102
- Status changed from New to Pending Backport
- Copied to Backport #59016: quincy: snap-schedule: handle non-existent path gracefully during snapshot creation added
- Copied to Backport #59017: pacific: snap-schedule: handle non-existent path gracefully during snapshot creation added
- Tags set to backport_processed
- Tags deleted (
backport_processed)
- Backport changed from pacific,quincy to reef,quincy,pacific
- Copied to Backport #59411: reef: snap-schedule: handle non-existent path gracefully during snapshot creation added
- Tags set to backport_processed
- Status changed from Pending Backport to Resolved
Also available in: Atom
PDF