Bug #43497
closedceph-volume lvm list $device doesn't work if $device is a symlink
0%
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.
Updated by Jan Fajerski over 4 years ago
- Status changed from New to Pending Backport
- Backport set to nautilus, mimic
- Pull request ID set to 32525
Updated by Nathan Cutler over 4 years ago
- Copied to Backport #43569: mimic: ceph-volume lvm list $device doesn't work if $device is a symlink added
Updated by Nathan Cutler over 4 years ago
- Copied to Backport #43570: nautilus: ceph-volume lvm list $device doesn't work if $device is a symlink added
Updated by Nathan Cutler over 4 years ago
- Project changed from Ceph to ceph-volume
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".