[Bug 1812935] Re: oslo cache mempool issues with python3
I can confirm it works. The rocky-proposed package python-oslo.cache-1.30.1-0ubuntu1.1 fixes bug #1822541 too. I manually upgraded the n-c-c units on a Rocky cloud (applying the proper bindings for n-c-c & memcached according with the comment #14 of bug #1823740) to get the new python-oslo packaged installed and now n-c-c fully works. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1812935 Title: oslo cache mempool issues with python3 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1812935/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1590689] Re: MAAS 1.9.3 + Juju 1.25.5 - on the Juju controller node eth0 and juju-br0 interfaces have the same IP address at the same time
the late_command curtin line should be also set in /etc/maas/preseeds/curtin_userdata -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1590689 Title: MAAS 1.9.3 + Juju 1.25.5 - on the Juju controller node eth0 and juju- br0 interfaces have the same IP address at the same time To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1590689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1675760] [NEW] rootfs issues - 2.8 LXD release
Public bug reported: System: Distributor ID: Ubuntu Description:Ubuntu 16.04.2 LTS Release:16.04 Codename: xenial Kernel release: 4.8.0-36 LXD release 2.8 I got a rootfs error starting few LXD containers: https://pastebin.canonical.com/183648/ This is the 'lxc list' output: https://pastebin.canonical.com/183650/ That container, named 'idm' uses an 'ovs' profile: https://pastebin.canonical.com/183649/ Here attached there is the /var/log/lxd/lxd.log file ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lxd 2.8-0ubuntu1~ubuntu16.04.1 ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11 Uname: Linux 4.8.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Fri Mar 24 12:22:59 2017 InstallationDate: Installed on 2017-03-23 (0 days ago) InstallationMedia: Ubuntu-Server 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.8) SourcePackage: lxd UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lxd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Attachment added: "LXD log file" https://bugs.launchpad.net/bugs/1675760/+attachment/4844335/+files/lxd.log.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1675760 Title: rootfs issues - 2.8 LXD release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1675760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1675760] Re: rootfs issues - 2.8 LXD release
We ran new tests: some issue shows up even using LXD 2.12 If I run: for X in `seq 1 4`; do lxc init ubuntu: test$X & done LXD creates the containers but it can't start them. This is the output of 'lxc info --show-log test1': https://pastebin.canonical.com/183666/ If I run: for X in `seq 1 4`; do lxc init ubuntu: test$X ; done there are no issues and I can start the containers in the usual way. Looks like LXD isn't able to handle some sort of concurrency during the containers creation. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1675760 Title: rootfs issues - 2.8 LXD release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1675760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1675760] Re: rootfs issues - 2.8 LXD release
A freshly created one (KVM VM). LXD 2.12 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1675760 Title: rootfs issues - 2.8 LXD release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1675760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1675760] Re: rootfs issues - 2.8 LXD release
'lxc info' output: http://pastebin.ubuntu.com/24241376/ 'lxc config show' output: http://pastebin.ubuntu.com/24241379/ I ran: for X in `seq 1 4`; do lxc init ubuntu: test$X & done and then, after a while: for X in `seq 1 4`; do lxc start test$X & done This is what I got in the /var/log/lxd/lxd.log file: http://pastebin.ubuntu.com/24241385/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1675760 Title: rootfs issues - 2.8 LXD release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1675760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1675760] Re: rootfs issues - 2.8 LXD release
cat /proc/self/mounts http://pastebin.ubuntu.com/24241515/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1675760 Title: rootfs issues - 2.8 LXD release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1675760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1675760] Re: rootfs issues - 2.8 LXD release
Here attached there is the log of a single container (test1), as requested by Christian. lxc info --show-log test1 ** Attachment added: "'test1' container log" https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1675760/+attachment/4844639/+files/test1.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1675760 Title: rootfs issues - 2.8 LXD release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1675760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1675760] Re: rootfs issues - 2.8 LXD release
VM upgraded to: Linux ubuntu 4.4.0-66-generic #87 Same behaviour. Here attached the output of the 'ls' commands. ** Attachment added: "lxd.listing" https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1675760/+attachment/4844752/+files/lxd.listing -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1675760 Title: rootfs issues - 2.8 LXD release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1675760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1675760] Re: rootfs issues - 2.8 LXD release
Yes, I unmounted it. getfacl: Removing leading '/' from absolute path names # file: var/lib/lxd/storage-pools/default/containers/test1 # owner: 10 # group: 10 user::rwx user:10:r-x group::r-x mask::r-x other::r-x -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1675760 Title: rootfs issues - 2.8 LXD release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1675760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1675760] Re: rootfs issues - 2.8 LXD release
Running the containers 'init' operation in the concurrent way and looking with a 'top', you can see the related 'unsquashfs' operations running: for X in `seq 1 4`; do lxc init ubuntu: test$X & done top Waiting until the unsquashfs terminates and then starting the containers, all is good and the operation runs fine: for X in `seq 1 4`; do lxc start test$X & done The 'init' process takes some time to explode the container image on the fs. Looks like there are not any bugs but all this behaviour is due to the overall speed (disk+fs) to unsquash the containers images. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1675760 Title: rootfs issues - 2.8 LXD release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1675760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1567578] [NEW] libnl should be updated to support up to 63 VFs per single PF
Public bug reported: Ubuntu 14.04.4 and SRIOV settings. As already documented in https://bugs.launchpad.net/mos/+bug/1501738 there is a bug in the default libnl library release installed on Ubuntu 14.04.4 The library release is the 3.2.21-1 and the bug is impacting on the maximum VFs number that can be enabled (up to 30) even if the PF supports up to 63 VFs in an Openstack SRIOV configuration The workaround is to install a newer library release, the 3.2.24-2: wget https://launchpad.net/ubuntu/+archive/primary/+files/libnl-3-200_3.2.24-2_amd64.deb wget https://launchpad.net/ubuntu/+archive/primary/+files/libnl-genl-3-200_3.2.24-2_amd64.deb wget https://launchpad.net/ubuntu/+archive/primary/+files/libnl-route-3-200_3.2.24-2_amd64.deb dpkg -i libnl-3-200_3.2.24-2_amd64.deb dpkg -i libnl-genl-3-200_3.2.24-2_amd64.deb dpkg -i libnl-route-3-200_3.2.24-2_amd64.deb ** Affects: libnl3 (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: 14.04.4 libnl nova-compute openstack sriov ubuntu vf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1567578 Title: libnl should be updated to support up to 63 VFs per single PF To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1567578/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
