[Bug 1842751] Re: [disco] [eoan] After unmount, cannot open /dev/vdb: Device or resource busy
> Hello - Does the recent switch from New -> Triaged for charm-cinder and charm-nova-compute mean that someone was able to determine that the charms are to blame and perhaps not the kernel? Sadly not; I'm just knocking them off new; the alternative is incomplete which means they'll time out after 60 days. As it is confirmed in the kernel, it may well be invalid for both charms. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842751 Title: [disco] [eoan] After unmount, cannot open /dev/vdb: Device or resource busy To manage notifications about this bug go to: https://bugs.launchpad.net/charm-cinder/+bug/1842751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842751] Re: [disco] [eoan] After unmount, cannot open /dev/vdb: Device or resource busy
Hello - Does the recent switch from New -> Triaged for charm-cinder and charm-nova-compute mean that someone was able to determine that the charms are to blame and perhaps not the kernel? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842751 Title: [disco] [eoan] After unmount, cannot open /dev/vdb: Device or resource busy To manage notifications about this bug go to: https://bugs.launchpad.net/charm-cinder/+bug/1842751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842751] Re: [disco] [eoan] After unmount, cannot open /dev/vdb: Device or resource busy
** Changed in: charm-cinder Status: New => Triaged ** Changed in: charm-nova-compute Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842751 Title: [disco] [eoan] After unmount, cannot open /dev/vdb: Device or resource busy To manage notifications about this bug go to: https://bugs.launchpad.net/charm-cinder/+bug/1842751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1842751] Re: [disco] [eoan] After unmount, cannot open /dev/vdb: Device or resource busy
On 2019-09-06 00:15:03, Ryan Beisner wrote: > We’ve just dug into this aspect of both Disco and Eoan. Unfortunately, > I don’t know if this ever succeeded on these two releases. I don't know if you're easily able to test old kernel versions but it could be helpful to test the kernel that Disco released with. That's kernel version 5.0.0-13.14. That kernel would not have this commit: https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/disco/commit/?id=13674c2ebe52da7c30cf27f9800d0624c63deb03 It doesn't look problematic to me but it is a commit shared between current Disco and Eoan kernels and intersects with the direct I/O operations that mkfs.xfs does on the block device. It is a reach but just knowing whether or not the Disco release kernel is affected would allow us to rule out (or not) any changes landed since the release. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842751 Title: [disco] [eoan] After unmount, cannot open /dev/vdb: Device or resource busy To manage notifications about this bug go to: https://bugs.launchpad.net/charm-cinder/+bug/1842751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842751] Re: [disco] [eoan] After unmount, cannot open /dev/vdb: Device or resource busy
We’ve just dug into this aspect of both Disco and Eoan. Unfortunately, I don’t know if this ever succeeded on these two releases. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842751 Title: [disco] [eoan] After unmount, cannot open /dev/vdb: Device or resource busy To manage notifications about this bug go to: https://bugs.launchpad.net/charm-cinder/+bug/1842751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842751] Re: [disco] [eoan] After unmount, cannot open /dev/vdb: Device or resource busy
Ryan, did this work on Eoan and Disco at some point in the past or is this the first time that you've tested this workflow on those releases? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842751 Title: [disco] [eoan] After unmount, cannot open /dev/vdb: Device or resource busy To manage notifications about this bug go to: https://bugs.launchpad.net/charm-cinder/+bug/1842751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842751] Re: [disco] [eoan] After unmount, cannot open /dev/vdb: Device or resource busy
I was unable to reproduce this in a Disco VM that I manually configured to mount an ext4 virtio-blk device at boot: $ dmesg | grep vdb [2.352490] virtio_blk virtio4: [vdb] 20971520 512-byte logical blocks (10.7 GB/10.0 GiB) [6.898149] EXT4-fs (vdb): mounted filesystem with ordered data mode. Opts: (null) tyhicks@sec-disco-amd64:~$ uname -a Linux sec-disco-amd64 5.0.0-27-generic #28-Ubuntu SMP Tue Aug 20 19:53:07 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux tyhicks@sec-disco-amd64:~$ lsb_release -c Codename: disco tyhicks@sec-disco-amd64:~$ sudo umount /mnt [sudo] password for tyhicks: tyhicks@sec-disco-amd64:~$ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sr0 11:01 1024M 0 rom vda252:00 16G 0 disk └─vda1 252:10 16G 0 part ├─vmtools--vg-root 253:00 15G 0 lvm / └─vmtools--vg-swap_1 253:10 980M 0 lvm [SWAP] vdb252:16 0 10G 0 disk tyhicks@sec-disco-amd64:~$ sudo mkfs.xfs -f -i size=1024 /dev/vdb meta-data=/dev/vdb isize=1024 agcount=4, agsize=655360 blks = sectsz=512 attr=2, projid32bit=1 = crc=1finobt=1, sparse=0, rmapbt=0, reflink=0 data = bsize=4096 blocks=2621440, imaxpct=25 = sunit=0 swidth=0 blks naming =version 2 bsize=4096 ascii-ci=0 ftype=1 log =internal log bsize=4096 blocks=2560, version=2 = sectsz=512 sunit=0 blks, lazy-count=1 realtime =none extsz=4096 blocks=0, rtextents=0 I manually ran those commands after the VM came up. This doesn't really rule anything out but might indicate that the more complex juju/OpenStack environment is needed to reproduce. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842751 Title: [disco] [eoan] After unmount, cannot open /dev/vdb: Device or resource busy To manage notifications about this bug go to: https://bugs.launchpad.net/charm-cinder/+bug/1842751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842751] Re: [disco] [eoan] After unmount, cannot open /dev/vdb: Device or resource busy
It is useful to note that the attached logs indicate that /dev/vdb2 is a virtio-blk device containing a mounted ext4 filesystem prior to it being unmounted and (attempted to be) reformatted with xfs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842751 Title: [disco] [eoan] After unmount, cannot open /dev/vdb: Device or resource busy To manage notifications about this bug go to: https://bugs.launchpad.net/charm-cinder/+bug/1842751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842751] Re: [disco] [eoan] After unmount, cannot open /dev/vdb: Device or resource busy
And Bionic for grins: ** Description changed: Disco and Eoan device is busy after unmounting an ephemeral disk, cannot format the device until rebooting. This is blocking all of OpenStack Charms which interact with block devices (Nova Compute, Ceph, Swift, Cinder), on the Disco and Eoan series. As we are nearing LTS-1, this will become urgent pretty quickly. Reproducer, on an OpenStack cloud: juju deploy cs:ubuntu ubuntu-bionic --series bionic juju deploy cs:ubuntu ubuntu-disco --series disco juju deploy cs:ubuntu ubuntu-eoan --series eoan Succeeds on Bionic: ubuntu@juju-8d01b7-foo-14:~$ uname -a Linux juju-8d01b7-foo-14 4.15.0-60-generic #67-Ubuntu SMP Thu Aug 22 16:55:30 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux ubuntu@juju-8d01b7-foo-14:~$ lsb_release -c Codename: bionic ubuntu@juju-8d01b7-foo-14:~$ lsblk NAMEMAJ:MIN RM SIZE RO TYPE MOUNTPOINT vda 252:00 20G 0 disk ├─vda1 252:10 19.9G 0 part / ├─vda14 252:14 04M 0 part └─vda15 252:15 0 106M 0 part /boot/efi vdb 252:16 0 40G 0 disk /mnt ubuntu@juju-8d01b7-foo-14:~$ df -h Filesystem Size Used Avail Use% Mounted on udev985M 0 985M 0% /dev tmpfs 200M 712K 199M 1% /run /dev/vda120G 1.7G 18G 9% / tmpfs 997M 0 997M 0% /dev/shm tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs 997M 0 997M 0% /sys/fs/cgroup /dev/vda15 105M 3.6M 101M 4% /boot/efi /dev/vdb 40G 49M 38G 1% /mnt tmpfs 100K 0 100K 0% /var/lib/lxd/shmounts tmpfs 100K 0 100K 0% /var/lib/lxd/devlxd tmpfs 200M 0 200M 0% /run/user/1000 ubuntu@juju-8d01b7-foo-14:~$ sudo umount /dev/vdb ubuntu@juju-8d01b7-foo-14:~$ sudo mkfs.xfs -f -i size=1024 /dev/vdb meta-data=/dev/vdb isize=1024 agcount=4, agsize=2621440 blks = sectsz=512 attr=2, projid32bit=1 = crc=1finobt=1, sparse=0, rmapbt=0, reflink=0 data = bsize=4096 blocks=10485760, imaxpct=25 = sunit=0 swidth=0 blks naming =version 2 bsize=4096 ascii-ci=0 ftype=1 log =internal log bsize=4096 blocks=5120, version=2 = sectsz=512 sunit=0 blks, lazy-count=1 realtime =none extsz=4096 blocks=0, rtextents=0 Fails on Disco: ubuntu@juju-8d01b7-foo-12:~$ uname -a Linux juju-8d01b7-foo-12 5.0.0-27-generic #28-Ubuntu SMP Tue Aug 20 19:53:07 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux ubuntu@juju-8d01b7-foo-12:~$ lsb_release -c Codename: disco ubuntu@juju-8d01b7-foo-12:~$ sudo umount /mnt ubuntu@juju-8d01b7-foo-12:~$ lsblk NAMEMAJ:MIN RM SIZE RO TYPE MOUNTPOINT loop0 7:00 88.7M 1 loop /snap/core/7396 loop1 7:10 54.5M 1 loop /snap/lxd/11727 vda 252:00 20G 0 disk ├─vda1 252:10 19.9G 0 part / ├─vda14 252:14 04M 0 part └─vda15 252:15 0 106M 0 part /boot/efi vdb 252:16 0 40G 0 disk ubuntu@juju-8d01b7-foo-12:~$ sudo mkfs.xfs -f -i size=1024 /dev/vdb mkfs.xfs: cannot open /dev/vdb: Device or resource busy Fails on Eoan: ubuntu@juju-8d01b7-foo-13:~$ sudo umount /mnt ubuntu@juju-8d01b7-foo-13:~$ lsblk NAMEMAJ:MIN RM SIZE RO TYPE MOUNTPOINT loop0 7:00 88.7M 1 loop /snap/core/7396 loop1 7:10 54.5M 1 loop /snap/lxd/11727 vda 252:00 20G 0 disk ├─vda1 252:10 19.9G 0 part / ├─vda14 252:14 04M 0 part └─vda15 252:15 0 106M 0 part /boot/efi vdb 252:16 0 40G 0 disk ubuntu@juju-8d01b7-foo-13:~$ sudo mkfs.xfs -f -i size=1024 /dev/vdb mkfs.xfs: cannot open /dev/vdb: Device or resource busy .. Original bug description: On disco-stein, hook failed: "config-changed" with mkfs.xfs: cannot open /dev/vdb: Device or resource busy https://openstack-ci- reports.ubuntu.com/artifacts/test_charm_pipeline_func_full/openstack /charm-cinder/678676/3/3803/index.html https://openstack-ci- reports.ubuntu.com/artifacts/test_charm_pipeline_func_full/openstack /charm-cinder/678676/3/3803/test_charm_func_full_7062/juju-status-zaza- 5b39f0208674.txt https://openstack-ci- reports.ubuntu.com/artifacts/test_charm_pipeline_func_full/openstack /charm-cinder/678676/3/3803/test_charm_func_full_7062/juju-crashdump- 7d3902a2-4fdf-435a-82c4-5d2ad9af4cb5.tar.xz 2019-09-03 21:33:27 DEBUG config-changed Unpacking apparmor-utils (2.13.2-9ubuntu6.1) ... 2019-09-03 21:33:27 DEBUG config-changed Setting up python3-libapparmor (2.13.2-9ubuntu6.1) ... 2019-09-03 21:33:27 DEBUG config-changed Setting up python3-apparmor (2.13.2-9ubuntu6.1) ... 2019-09-03 21:33:27 DEBUG
[Bug 1842751] Re: [disco] [eoan] After unmount, cannot open /dev/vdb: Device or resource busy
^ Disco apport above, Eoan to follow: ** Tags added: eoan ** Description changed: Disco and Eoan device is busy after unmounting an ephemeral disk, cannot format the device until rebooting. This is blocking all of OpenStack Charms which interact with block devices (Nova Compute, Ceph, Swift, Cinder), on the Disco and Eoan series. As we are nearing LTS-1, this will become urgent pretty quickly. Reproducer, on an OpenStack cloud: juju deploy cs:ubuntu ubuntu-bionic --series bionic juju deploy cs:ubuntu ubuntu-disco --series disco juju deploy cs:ubuntu ubuntu-eoan --series eoan Succeeds on Bionic: ubuntu@juju-8d01b7-foo-14:~$ uname -a Linux juju-8d01b7-foo-14 4.15.0-60-generic #67-Ubuntu SMP Thu Aug 22 16:55:30 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux ubuntu@juju-8d01b7-foo-14:~$ lsb_release -c Codename: bionic ubuntu@juju-8d01b7-foo-14:~$ lsblk NAMEMAJ:MIN RM SIZE RO TYPE MOUNTPOINT vda 252:00 20G 0 disk ├─vda1 252:10 19.9G 0 part / ├─vda14 252:14 04M 0 part └─vda15 252:15 0 106M 0 part /boot/efi vdb 252:16 0 40G 0 disk /mnt ubuntu@juju-8d01b7-foo-14:~$ df -h Filesystem Size Used Avail Use% Mounted on udev985M 0 985M 0% /dev tmpfs 200M 712K 199M 1% /run /dev/vda120G 1.7G 18G 9% / tmpfs 997M 0 997M 0% /dev/shm tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs 997M 0 997M 0% /sys/fs/cgroup /dev/vda15 105M 3.6M 101M 4% /boot/efi /dev/vdb 40G 49M 38G 1% /mnt tmpfs 100K 0 100K 0% /var/lib/lxd/shmounts tmpfs 100K 0 100K 0% /var/lib/lxd/devlxd tmpfs 200M 0 200M 0% /run/user/1000 ubuntu@juju-8d01b7-foo-14:~$ sudo umount /dev/vdb ubuntu@juju-8d01b7-foo-14:~$ sudo mkfs.xfs -f -i size=1024 /dev/vdb meta-data=/dev/vdb isize=1024 agcount=4, agsize=2621440 blks = sectsz=512 attr=2, projid32bit=1 = crc=1finobt=1, sparse=0, rmapbt=0, reflink=0 data = bsize=4096 blocks=10485760, imaxpct=25 = sunit=0 swidth=0 blks naming =version 2 bsize=4096 ascii-ci=0 ftype=1 log =internal log bsize=4096 blocks=5120, version=2 = sectsz=512 sunit=0 blks, lazy-count=1 realtime =none extsz=4096 blocks=0, rtextents=0 Fails on Disco: ubuntu@juju-8d01b7-foo-12:~$ uname -a Linux juju-8d01b7-foo-12 5.0.0-27-generic #28-Ubuntu SMP Tue Aug 20 19:53:07 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux ubuntu@juju-8d01b7-foo-12:~$ lsb_release -c Codename: disco ubuntu@juju-8d01b7-foo-12:~$ sudo umount /mnt ubuntu@juju-8d01b7-foo-12:~$ lsblk NAMEMAJ:MIN RM SIZE RO TYPE MOUNTPOINT loop0 7:00 88.7M 1 loop /snap/core/7396 loop1 7:10 54.5M 1 loop /snap/lxd/11727 vda 252:00 20G 0 disk ├─vda1 252:10 19.9G 0 part / ├─vda14 252:14 04M 0 part └─vda15 252:15 0 106M 0 part /boot/efi vdb 252:16 0 40G 0 disk ubuntu@juju-8d01b7-foo-12:~$ sudo mkfs.xfs -f -i size=1024 /dev/vdb mkfs.xfs: cannot open /dev/vdb: Device or resource busy Fails on Eoan: ubuntu@juju-8d01b7-foo-13:~$ sudo umount /mnt ubuntu@juju-8d01b7-foo-13:~$ lsblk NAMEMAJ:MIN RM SIZE RO TYPE MOUNTPOINT loop0 7:00 88.7M 1 loop /snap/core/7396 loop1 7:10 54.5M 1 loop /snap/lxd/11727 vda 252:00 20G 0 disk ├─vda1 252:10 19.9G 0 part / ├─vda14 252:14 04M 0 part └─vda15 252:15 0 106M 0 part /boot/efi vdb 252:16 0 40G 0 disk ubuntu@juju-8d01b7-foo-13:~$ sudo mkfs.xfs -f -i size=1024 /dev/vdb mkfs.xfs: cannot open /dev/vdb: Device or resource busy .. Original bug description: On disco-stein, hook failed: "config-changed" with mkfs.xfs: cannot open /dev/vdb: Device or resource busy https://openstack-ci- reports.ubuntu.com/artifacts/test_charm_pipeline_func_full/openstack /charm-cinder/678676/3/3803/index.html https://openstack-ci- reports.ubuntu.com/artifacts/test_charm_pipeline_func_full/openstack /charm-cinder/678676/3/3803/test_charm_func_full_7062/juju-status-zaza- 5b39f0208674.txt https://openstack-ci- reports.ubuntu.com/artifacts/test_charm_pipeline_func_full/openstack /charm-cinder/678676/3/3803/test_charm_func_full_7062/juju-crashdump- 7d3902a2-4fdf-435a-82c4-5d2ad9af4cb5.tar.xz 2019-09-03 21:33:27 DEBUG config-changed Unpacking apparmor-utils (2.13.2-9ubuntu6.1) ... 2019-09-03 21:33:27 DEBUG config-changed Setting up python3-libapparmor (2.13.2-9ubuntu6.1) ... 2019-09-03 21:33:27 DEBUG config-changed Setting up python3-apparmor
[Bug 1842751] Re: [disco] [eoan] After unmount, cannot open /dev/vdb: Device or resource busy
apport information ** Tags added: apport-collected disco ec2-images ** Description changed: Disco and Eoan device is busy after unmounting an ephemeral disk, cannot format the device until rebooting. This is blocking all of OpenStack Charms which interact with block devices (Nova Compute, Ceph, Swift, Cinder), on the Disco and Eoan series. As we are nearing LTS-1, this will become urgent pretty quickly. Reproducer, on an OpenStack cloud: juju deploy cs:ubuntu ubuntu-bionic --series bionic juju deploy cs:ubuntu ubuntu-disco --series disco juju deploy cs:ubuntu ubuntu-eoan --series eoan Succeeds on Bionic: ubuntu@juju-8d01b7-foo-14:~$ uname -a Linux juju-8d01b7-foo-14 4.15.0-60-generic #67-Ubuntu SMP Thu Aug 22 16:55:30 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux ubuntu@juju-8d01b7-foo-14:~$ lsb_release -c Codename: bionic ubuntu@juju-8d01b7-foo-14:~$ lsblk NAMEMAJ:MIN RM SIZE RO TYPE MOUNTPOINT vda 252:00 20G 0 disk ├─vda1 252:10 19.9G 0 part / ├─vda14 252:14 04M 0 part └─vda15 252:15 0 106M 0 part /boot/efi vdb 252:16 0 40G 0 disk /mnt ubuntu@juju-8d01b7-foo-14:~$ df -h Filesystem Size Used Avail Use% Mounted on udev985M 0 985M 0% /dev tmpfs 200M 712K 199M 1% /run /dev/vda120G 1.7G 18G 9% / tmpfs 997M 0 997M 0% /dev/shm tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs 997M 0 997M 0% /sys/fs/cgroup /dev/vda15 105M 3.6M 101M 4% /boot/efi /dev/vdb 40G 49M 38G 1% /mnt tmpfs 100K 0 100K 0% /var/lib/lxd/shmounts tmpfs 100K 0 100K 0% /var/lib/lxd/devlxd tmpfs 200M 0 200M 0% /run/user/1000 ubuntu@juju-8d01b7-foo-14:~$ sudo umount /dev/vdb ubuntu@juju-8d01b7-foo-14:~$ sudo mkfs.xfs -f -i size=1024 /dev/vdb meta-data=/dev/vdb isize=1024 agcount=4, agsize=2621440 blks = sectsz=512 attr=2, projid32bit=1 = crc=1finobt=1, sparse=0, rmapbt=0, reflink=0 data = bsize=4096 blocks=10485760, imaxpct=25 = sunit=0 swidth=0 blks naming =version 2 bsize=4096 ascii-ci=0 ftype=1 log =internal log bsize=4096 blocks=5120, version=2 = sectsz=512 sunit=0 blks, lazy-count=1 realtime =none extsz=4096 blocks=0, rtextents=0 Fails on Disco: ubuntu@juju-8d01b7-foo-12:~$ uname -a Linux juju-8d01b7-foo-12 5.0.0-27-generic #28-Ubuntu SMP Tue Aug 20 19:53:07 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux ubuntu@juju-8d01b7-foo-12:~$ lsb_release -c Codename: disco ubuntu@juju-8d01b7-foo-12:~$ sudo umount /mnt ubuntu@juju-8d01b7-foo-12:~$ lsblk NAMEMAJ:MIN RM SIZE RO TYPE MOUNTPOINT loop0 7:00 88.7M 1 loop /snap/core/7396 loop1 7:10 54.5M 1 loop /snap/lxd/11727 vda 252:00 20G 0 disk ├─vda1 252:10 19.9G 0 part / ├─vda14 252:14 04M 0 part └─vda15 252:15 0 106M 0 part /boot/efi vdb 252:16 0 40G 0 disk ubuntu@juju-8d01b7-foo-12:~$ sudo mkfs.xfs -f -i size=1024 /dev/vdb mkfs.xfs: cannot open /dev/vdb: Device or resource busy Fails on Eoan: ubuntu@juju-8d01b7-foo-13:~$ sudo umount /mnt ubuntu@juju-8d01b7-foo-13:~$ lsblk NAMEMAJ:MIN RM SIZE RO TYPE MOUNTPOINT loop0 7:00 88.7M 1 loop /snap/core/7396 loop1 7:10 54.5M 1 loop /snap/lxd/11727 vda 252:00 20G 0 disk ├─vda1 252:10 19.9G 0 part / ├─vda14 252:14 04M 0 part └─vda15 252:15 0 106M 0 part /boot/efi vdb 252:16 0 40G 0 disk ubuntu@juju-8d01b7-foo-13:~$ sudo mkfs.xfs -f -i size=1024 /dev/vdb mkfs.xfs: cannot open /dev/vdb: Device or resource busy .. Original bug description: On disco-stein, hook failed: "config-changed" with mkfs.xfs: cannot open /dev/vdb: Device or resource busy https://openstack-ci- reports.ubuntu.com/artifacts/test_charm_pipeline_func_full/openstack /charm-cinder/678676/3/3803/index.html https://openstack-ci- reports.ubuntu.com/artifacts/test_charm_pipeline_func_full/openstack /charm-cinder/678676/3/3803/test_charm_func_full_7062/juju-status-zaza- 5b39f0208674.txt https://openstack-ci- reports.ubuntu.com/artifacts/test_charm_pipeline_func_full/openstack /charm-cinder/678676/3/3803/test_charm_func_full_7062/juju-crashdump- 7d3902a2-4fdf-435a-82c4-5d2ad9af4cb5.tar.xz 2019-09-03 21:33:27 DEBUG config-changed Unpacking apparmor-utils (2.13.2-9ubuntu6.1) ... 2019-09-03 21:33:27 DEBUG config-changed Setting up python3-libapparmor (2.13.2-9ubuntu6.1) ... 2019-09-03 21:33:27 DEBUG config-changed Setting up python3-apparmor
[Bug 1842751] Re: [disco] [eoan] After unmount, cannot open /dev/vdb: Device or resource busy
Similar behaviour documented in this bug for ceph-mon and ceph-osd with disco series. https://bugs.launchpad.net/charm-ceph-mon/+bug/1842498. Might be a duplicate if the underlying cause is the same -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842751 Title: [disco] [eoan] After unmount, cannot open /dev/vdb: Device or resource busy To manage notifications about this bug go to: https://bugs.launchpad.net/charm-cinder/+bug/1842751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842751] Re: [disco] [eoan] After unmount, cannot open /dev/vdb: Device or resource busy
** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842751 Title: [disco] [eoan] After unmount, cannot open /dev/vdb: Device or resource busy To manage notifications about this bug go to: https://bugs.launchpad.net/charm-cinder/+bug/1842751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
