** Description changed:
[Impact]
- * On Xenial after installing lvm2, you must reboot before you are able to
run vgcreate.
- * The package installer should be starting lvmetad.service.
- * $ sudo vgcreate localvg
- /run/lvm/lvmetad.socket: connect failed: No such file or directory
-
I actually also tested this on recent cloud-images of yakkety, and I'm
seeing the same thing. That may be a separate issue though as reboot
does not fix it there.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in
I just installed yakkety, and got a similar result. All of the cloud-
images and maas images have lvm2 already built in, so this would not be
seen there.
$ sudo vgcreate localvg
Command failed with status code 5.
I installed yakkety like this.
#!/bin/bash
virt-install \
--connect
I cannot recreate this on yakkety, there lvm2-lvmetad.socket starts up
just fine right after package installation. Can you confirm?
** Changed in: lvm2 (Ubuntu)
Status: Triaged => Fix Released
** Changed in: lvm2 (Ubuntu Xenial)
Status: New => Triaged
--
You received this bug
Indeed the generated /var/lib/dpkg/info/lvm2.postinst does not start
lvm2-lvmetad.socket at all, even though debian/rules calls
dh_systemd_start --restart-after-upgrade \
lvm2-lvmetad.service \
lvm2-lvmpolld.service
dh_systemd_start --no-restart-on-upgrade \
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: lvm2 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
6 matches
Mail list logo
