View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0017097 | CentOS-8 | libvirt | public | 2020-02-28 19:30 | 2020-02-28 19:30 |
| Reporter | tizo | ||||
| Priority | high | Severity | major | Reproducibility | always |
| Status | new | Resolution | open | ||
| Product Version | 8.1.1911 | ||||
| Target Version | Fixed in Version | ||||
| Summary | 0017097: Worng parameters of vgchange when libvirt tries to start an LVM pool of a shared VG | ||||
| Description | When libvirt tries to start an LVM pool, it always use "/usr/sbin/vgchange -aly vg-name". This used to be good for clustered VG (based on clvm, that afaics is being deprecated in favor of lvmlockd). However, when the VG is a shared VG (based on lvmlockd), this fail with the message "Failed to lock logical volume....". Maybe a solution could be to let the users modify the vgchange parameters for libvirtd. | ||||
| Steps To Reproduce | * Create a shared VG with lvmlockd. * Add it as a pool for libvirtd, with "virsh pool-define" for example. * Try to start it with "virsh pool-start". | ||||
| Tags | No tags attached. | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2020-02-28 19:30 | tizo | New Issue |
