Project

General

Profile

Actions
Copy link

Bug #62218

open

mgr/snap_schedule: missing fs argument on command-line gives unexpected results

Added by Milind Changire 9 months ago. Updated 7 months ago.

Status:
Pending Backport
Priority:
Normal
Assignee:
Milind Changire
Category:
-
Target version:
-
% Done:

0%

Source:
Tags:
backport_processed
Backport:
reef,quincy
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(FS):
mgr/snap_schedule
Labels (FS):
Pull request ID:
52686
Crash signature (v1):
Crash signature (v2):

Description

The first fs in the fsmap is taken as the default fs for all snap_schedule commands.
This leads to unexpected results if the fs argument is skipped unintentionally and leads to work loss.

Related issues 2 (2 open — 0 closed)

Copied to CephFS - Backport #63241: quincy: mgr/snap_schedule: missing fs argument on command-line gives unexpected resultsIn ProgressMilind ChangireActions
Copied to CephFS - Backport #63242: reef: mgr/snap_schedule: missing fs argument on command-line gives unexpected resultsIn ProgressMilind ChangireActions
Actions
Copy link
 #1

Updated by Milind Changire 9 months ago

  • Status changed from New to Fix Under Review
  • Pull request ID set to 52686
Actions
Copy link
 #2

Updated by Milind Changire 9 months ago

  • Assignee set to Milind Changire
Actions
Copy link
 #3

Updated by Venky Shankar 7 months ago

  • Status changed from Fix Under Review to Pending Backport
  • Backport set to reef,quincy
Actions
Copy link
 #4

Updated by Backport Bot 7 months ago

  • Copied to Backport #63241: quincy: mgr/snap_schedule: missing fs argument on command-line gives unexpected results added
Actions
Copy link
 #5

Updated by Backport Bot 7 months ago

  • Copied to Backport #63242: reef: mgr/snap_schedule: missing fs argument on command-line gives unexpected results added
Actions
Copy link
 #6

Updated by Backport Bot 7 months ago

  • Tags set to backport_processed
Actions
Copy link

Also available in: Atom PDF