Project

General

Profile

Bug #36246

confusing message when running a 'ceph-volume scan'

Added by Guillaume Abrioux 3 months ago. Updated about 1 month ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
09/28/2018
Due date:
% Done:

0%

Source:
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:

Description

running a scan on a ceph-disk prepared OSD device returns this output :

[root@ceph-osd0 ~]# ceph-volume simple scan --stdout /dev/sda1
Running command: /usr/sbin/cryptsetup status /dev/sda1
stderr: Device sda1 not found {
"active": "ok",
"ceph_fsid": "54e4514e-b4d6-48c7-8ac6-78e5a586a1d3",
"cluster_name": "ceph",
"data": {
"path": "/dev/sda1",
"uuid": "f6ca964e-0801-4ad1-9d94-3688f403e105"
},
"fsid": "f6ca964e-0801-4ad1-9d94-3688f403e105",
"journal": {
"path": "/dev/disk/by-partuuid/cd63a661-8bb2-40e1-a311-9b8bc163bb8b",
"uuid": "cd63a661-8bb2-40e1-a311-9b8bc163bb8b"
},
"journal_uuid": "cd63a661-8bb2-40e1-a311-9b8bc163bb8b",
"keyring": "AQC+v6xbHZGjGRAAV6eznq/YbRdWtWIo+DiYEw==",
"magic": "ceph osd volume v026",
"ready": "ready",
"systemd": "",
"type": "filestore",
"whoami": 5
}

I bet there is no real bug here but the message "stderr: Device sda1 not found" is quite confusing.
I guess this is the output returned by `/usr/sbin/cryptsetup status /dev/sda1`, in that case ceph-volume should probably tell us something like "INFO: cryptsetup status failed on sda1, not a dmcrypt device".

History

#1 Updated by Alfredo Deza 2 months ago

  • Status changed from New to In Progress

#2 Updated by Alfredo Deza about 1 month ago

  • Status changed from In Progress to Resolved

mimic PR:https://github.com/ceph/ceph/pull/24826
luminous PR: https://github.com/ceph/ceph/pull/24827

Also available in: Atom PDF