Project

General

Profile

Actions
Copy link

Bug #43105

closed

batch silently changes OSD type in non-interactive mode

Added by Jan Fajerski over 4 years ago. Updated about 4 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Target version:
-
% Done:

0%

Source:
Tags:
Backport:
nautilus, mimic
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
31978
Crash signature (v1):
Crash signature (v2):

Description

If a batch call specifies an explicit db device (or wal or journal) and non-interactive (--yes) it can happen that the additional device gets filtered due to it being deemed unavailable. In this case the users wants a hybrid OSD but ends up with a standalone OSD without any further notification.

If this happens in standalone mode, we should fail that call.

Related issues 2 (0 open — 2 closed)

Copied to ceph-volume - Backport #43853: nautilus: batch silently changes OSD type in non-interactive modeResolvedJan FajerskiActions
Copied to ceph-volume - Backport #43854: mimic: batch silently changes OSD type in non-interactive modeResolvedJan FajerskiActions
Actions
Copy link
 #1

Updated by Jan Fajerski over 4 years ago

  • Backport set to nautilus, mimic
  • Pull request ID set to 31978
Actions
Copy link
 #2

Updated by Jan Fajerski over 4 years ago

  • Status changed from New to Pending Backport
Actions
Copy link
 #3

Updated by Nathan Cutler over 4 years ago

  • Copied to Backport #43853: nautilus: batch silently changes OSD type in non-interactive mode added
Actions
Copy link
 #4

Updated by Nathan Cutler over 4 years ago

  • Copied to Backport #43854: mimic: batch silently changes OSD type in non-interactive mode added
Actions
Copy link
 #5

Updated by Nathan Cutler about 4 years ago

  • 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".

Actions
Copy link

Also available in: Atom PDF