Project

General

Profile

Actions

Bug #43497

closed

ceph-volume lvm list $device doesn't work if $device is a symlink

Added by BenoƮt Knecht 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:
Crash signature (v1):
Crash signature (v2):

Description

Assuming that `/dev/disk/by-path/pci-0000:00:00.0` is a symlink to `/dev/sda`, and that `/dev/sda` contains a Ceph logical volume, I would expect

```
ceph-volume lvm list /dev/disk/by-path/pci-0000:00:00.0
```

to return the same as

```
ceph-volume lvm list /dev/sda
```

But it doesn't; the former returns `No valid Ceph devices found`, while the latter returns the expected device information.

This has the unfortunate side-effect of breaking Ceph-Ansible idem-potency when `lvm_devices` are specified using `/dev/disk/by-path/*` devices. In that case, the first Ceph-Ansible run works, but second run fails because the playbooks use `ceph-volume lvm list $device` to determine if `$device` is already part of an OSD; because of this issue, they think it isn't and try to add it a second time, which obviously fails.


Related issues 2 (0 open2 closed)

Copied to ceph-volume - Backport #43569: mimic: ceph-volume lvm list $device doesn't work if $device is a symlinkResolvedActions
Copied to ceph-volume - Backport #43570: nautilus: ceph-volume lvm list $device doesn't work if $device is a symlinkResolvedActions
Actions

Also available in: Atom PDF