Bug #23497
closedceph-volume: lvcreate: unrecognized option '--yes'
0%
Description
Running Luminous 12.2.4++ on Ubuntu Trusty 14.0.4.5
Trusty shipped with LVM 2.02.98.
LVM 2.02.99 added --yes for lvcreate (and many other commands)
root@cephstore12145:/# ceph-volume lvm create --filestore --journal /dev/nvme0n1p65 --data /dev/sde --dmcrypt
Running command: ceph-authtool --gen-print-key
Running command: ceph-authtool --gen-print-key
Running command: ceph --cluster ceph --name client.bootstrap-osd --keyring /var/lib/ceph/bootstrap-osd/ceph.keyring i - osd new 8678d0e2-fddc-4103-9141-bf8a92aee973> Was unable to complete a new OSD, will rollback changes
stderr: lsblk: unknown column: PKNAME,PARTLABEL
stderr: lsblk: unknown column: PKNAME,PARTLABEL
Running command: vgcreate --force --yes ceph-7edc3c91-1c72-4e87-8a47-af786c2c78ef /dev/sde
stderr: No physical volume label read from /dev/sde
stdout: Physical volume "/dev/sde" successfully created
stdout: Volume group "ceph-7edc3c91-1c72-4e87-8a47-af786c2c78ef" successfully created
Running command: lvcreate --yes -l 100%FREE -n osd-data-8678d0e2-fddc-4103-9141-bf8a92aee973 ceph-7edc3c91-1c72-4e87-8a47-af786c2c78ef
stderr: lvcreate: unrecognized option '--yes'
Error during parsing of command line.
-
--> OSD will be fully purged from the cluster, because the ID was generated
Running command: ceph osd purge osd.110 --yes-i-really-mean-it
stderr: purged osd.110
--> RuntimeError: command returned non-zero exit status: 3
Updated by Alfredo Deza about 6 years ago
- Status changed from New to Closed
ceph-volume does not support trusty because it relies on systemd which is not in Trusty.
We somehow missed the window to add a warning on this (for Trusty users)
Updated by Alfredo Deza about 6 years ago
- Status changed from Closed to In Progress
- Assignee set to Alfredo Deza
Trusty EOL is set for April of 2019, so we still have time to add the warning in ceph-volume.
Re-opening so that we can properly notify this on the next release
Updated by Alfredo Deza over 4 years ago
- Status changed from In Progress to Closed
Closing this as Trusty is already EOL. We never ended up implementing a check for this.