Actions
Bug #43105
closedbatch silently changes OSD type in non-interactive mode
Status:
Resolved
Priority:
Normal
Assignee:
-
Target version:
-
% Done:
0%
Source:
Tags:
Backport:
nautilus, mimic
Regression:
No
Severity:
3 - minor
Reviewed:
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.
Actions