[Bug 1657646] Re: VG/LV are not available in /dev/mapper/ after reboot

2017-06-20 Thread Andreas Hasenack
@paelzer noted this in his comment #5: """ First of all thin provisioning is not mainstream, the dependency is only a suggest, so install the tools $ sudo apt-get install thin-provisioning-tools """ ** Changed in: docker.io (Ubuntu) Status: New => Triaged ** Summary changed: - VG/LV

[Bug 1657646] Re: VG/LV are not available in /dev/mapper/ after reboot

2017-06-20 Thread Andreas Hasenack
@paelzer noted this in his comment #5: """ First of all thin provisioning is not mainstream, the dependency is only a suggest, so install the tools $ sudo apt-get install thin-provisioning-tools """ ** Changed in: docker.io (Ubuntu) Status: New => Triaged ** Summary changed: - VG/LV

[Bug 1657646] Re: VG/LV are not available in /dev/mapper/ after reboot

2017-06-20 Thread Andreas Hasenack
TL;DR "sudo apt install thin-provisioning-tools" fixes it. Adding debugging steps here for posterity. ubuntu@15-89:~$ cat /etc/docker/daemon.json { "storage-driver": "devicemapper", "storage-opts": [ "dm.thinpooldev=/dev/mapper/docker--storage-thinpool",

[Bug 1657646] Re: VG/LV are not available in /dev/mapper/ after reboot

2017-06-20 Thread Andreas Hasenack
TL;DR "sudo apt install thin-provisioning-tools" fixes it. Adding debugging steps here for posterity. ubuntu@15-89:~$ cat /etc/docker/daemon.json { "storage-driver": "devicemapper", "storage-opts": [ "dm.thinpooldev=/dev/mapper/docker--storage-thinpool",

[Bug 1657646] Re: VG/LV are not available in /dev/mapper/ after reboot

2017-05-12 Thread ChristianEhrhardt
Thanks for providing the steps, I have no time to set this up "right now" but 'm setting it back to new to mark that we are no more waiting on info from you until further analyzed. ** Changed in: docker.io (Ubuntu) Status: Incomplete => New -- You received this bug notification because

[Bug 1657646] Re: VG/LV are not available in /dev/mapper/ after reboot

2017-02-22 Thread ChristianEhrhardt
Hi, the proxy did well at hiding your actual reply by quoting my full pust. But since you asked for updates I have to kindly ask you instead - please read my detailed repro approach in comment #5 (things just worked for me). It is ending with: > Could you either > 1. report your exact steps on

[Bug 1657646] Re: VG/LV are not available in /dev/mapper/ after reboot

2017-02-09 Thread Tianon Gravi
** Package changed: docker (Ubuntu) => docker.io (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1657646 Title: VG/LV are not available in /dev/mapper/ after reboot To manage notifications

[Bug 1657646] Re: VG/LV are not available in /dev/mapper/ after reboot

2017-01-26 Thread Jon Grimm
** Changed in: docker (Ubuntu) Assignee: Jon Grimm (jgrimm) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1657646 Title: VG/LV are not available in /dev/mapper/ after reboot

[Bug 1657646] Re: VG/LV are not available in /dev/mapper/ after reboot

2017-01-25 Thread ChristianEhrhardt
Internal: for anyone else debugging on this, the mentioned test setup is on Diamond in guest "paelzer-testlvm-xenial" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1657646 Title: VG/LV are not

[Bug 1657646] Re: VG/LV are not available in /dev/mapper/ after reboot

2017-01-25 Thread ChristianEhrhardt
I tried to recreate. Note: as it was reported on power + Xenial this test was done on ppc64el Xenial as of today To do so with as much debugging as possible I created a normal Xenial KVM Guest via $ uvt-kvm create --cpu 4 --password=ubuntu paelzer-testlvm-xenial release=xenial Then I added a