[Bug 2063512] Re: on reboot with linux-image-6.5.0-34 system hangs at loading initial ramdisk
Doesn't seem to be related to « nvidia » : bigbob@bigbob-t480s:~$ dpkg -l | grep nvidia bigbob@bigbob-t480s:~$ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063512 Title: on reboot with linux-image-6.5.0-34 system hangs at loading initial ramdisk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-545/+bug/2063512/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959993] Re: SRU of LXC 4.0.12 to focal (upstream bugfix release)
Have confirmed the packages to be functional on both focal and impish. Tried installation, upgrade and basic container creation, deletion and normal operations. ** Tags removed: verification-needed-focal verification-needed-impish ** Tags added: verification-done-focal verification-done-impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959993 Title: SRU of LXC 4.0.12 to focal (upstream bugfix release) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1959993/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975736] Re: stateful snapshot not working
Hello, We usually prefer for support questions to be asked at https://discuss.linuxcontainers.org and issues be filed at https://github.com/lxc/lxd/issues. We only really look at Launchpad for bugs in the LXD deb which these days is limited to Ubuntu 18.04 as everything afterwards is using the snap. In this particular instance, you're most likely dealing with an outdated LXD agent setup which is keeping the 9p mount active and preventing the stateful snapshot. You may be able to update the setup by running: - cd /run/lxd_agent - ./install.sh - reboot This should refresh the systemd units used to start the agent with a current version. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975736 Title: stateful snapshot not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1975736/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971978] Re: Driver binaries fail to load on arm64 through LXD
For nvidia.runtime=true to work, you need an NVIDIA driver as well as the CUDA library on the host. The libnvidia-container part is identical on both architectures and has been used by Anbox before, so we're pretty confident it works. Just not on 22.04 hosts. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971978 Title: Driver binaries fail to load on arm64 through LXD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-510/+bug/1971978/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971978] Re: Driver binaries fail to load on arm64 through LXD
Right, nvidia-container-cli is specifically designed to use files from the host (outside of snap environment) as the files it loads (through dlopen) cannot be bundled (cuda, driver files, ...). nvidia-container-cli has logic to effectively chroot prior to processing any of the dlopen. It's then expected that the driver libraries on the host are generally built conservatively and can be loaded even by a slightly older version. It's true that moving LXD to core22 would certainly solve the error here, though it would trade it for another problem, which is that those same libraries, which nvidia-container-cli passes through to the container would then only work on 22.04 containers or up. On amd64 22.04, this all works, including passing through the driver libraries and binaries from the host to a container as old as Ubuntu 18.04. So something weird happened with the equivalent arm64 build here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971978 Title: Driver binaries fail to load on arm64 through LXD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-510/+bug/1971978/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971571] Re: ubuntu 22.04 cgroup2 works for clean install but upgrade to 22.04 causes cgroup2 problems
Can you show: - cat /proc/self/cgroup - cat /proc/self/mounts On a broken system? ** Changed in: lxd (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971571 Title: ubuntu 22.04 cgroup2 works for clean install but upgrade to 22.04 causes cgroup2 problems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1971571/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950282] Re: Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support
Latest FM350 is FR 1.26.13 (equivalent to 81600..00.29.19.16_5000..036.000.036_C40). Intel clarified that we should get that firmware from Fibocom and use that for testing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950282 Title: Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1950282/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1649094] Re: error message when trying to snapshot a non-existent container could be better
stgraber@dakara:~$ lxc snapshot does-not-exist snap0 Error: Instance not found ** Changed in: lxd (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1649094 Title: error message when trying to snapshot a non-existent container could be better To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1649094/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964833] Re: Disable "latest" as upgrade option on focal
** Changed in: lxd (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964833 Title: Disable "latest" as upgrade option on focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1964833/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969774] Re: riscv64: Failed creating instance record: Requested architecture isn't supported by this host
`images:` never had any riscv64 image. When that happens, the image selector downloads the closest image available which in this case is an amd64 image. ** Changed in: lxd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969774 Title: riscv64: Failed creating instance record: Requested architecture isn't supported by this host To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1969774/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969774] Re: riscv64: Failed creating instance record: Requested architecture isn't supported by this host
This is normal behavior when no image can be found for the local architecture. images: doesn't have any riscv64 images. ubuntu: only has 21.10 ubuntu-daily: has 22.04 ** Changed in: lxd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969774 Title: riscv64: Failed creating instance record: Requested architecture isn't supported by this host To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1969774/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966499] Re: Recent 5.13 kernel has broken KVM support
Works great on my side with the 5.13.0-41.46 kernel. VM start correctly and no more log spamming. ** Tags removed: verification-needed-impish ** Tags added: verification-done-impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966499 Title: Recent 5.13 kernel has broken KVM support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966499/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965901] Re: SRU the new 1.18 serie to focal for hwe
** Description changed: [Impact] We want to update to the newer serie for better hardware support + (support for Quectel EM120R-GL and EM160R-GL) [Test Plan] - * install modemmanager, libmbim, and libqmi from -proposed - * reboot and try WWAN function to see if any regression there. - * perform general dogfooding of its reverse dependencies (network- -manager, gnome-control-center etc.) + * install modemmanager, libmbim, and libqmi from -proposed + * reboot and try WWAN function to see if any regression there. + * perform general dogfooding of its reverse dependencies (network- + manager, gnome-control-center etc.) [Where problems could occur] The new version no longer automatically performs the FCC unlock procedure by default, see details on https://modemmanager.org/docs/modemmanager/fcc-unlock/ It means some modem will stop working out of the box. - - + Users can manually install the unlock utility as described in the "FCC unlock procedures in ModemManager >= 1.18.4" section in the page above. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965901 Title: SRU the new 1.18 serie to focal for hwe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/1965901/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967620] [NEW] [FFe] LXC 5.0 LTS
Public bug reported: LXC 5.0 LTS will very soon be released. The upstream release has been held up due to an incomplete port to meson (and deprecation of autotools), it's otherwise been ready to go for a few months. As far as LXC releases go, it's a very light one. Comparing it to current 4.0.12, we have: - No liblxc API changes at all (no new symbols or changes to headers) - Addition of a few configuration keys: - lxc.cgroup.dir.monitor.pivot - lxc.cgroup.dir.monitor - lxc.cgroup.dir.container.inner - lxc.cgroup.dir.container - lxc.time.offset.boot - lxc.time.offset.monotonic - veth.n_rxqueues - veth.n_txqueues - veth.vlan.id - veth.vlan.tagged.id - Port to meson (replacing autotools) Diffstat: ``` stgraber@dakara:~/data/code/lxc/lxc (lxc/master)$ git diff lxc-4.0.12.. . | diffstat .gitignore |1 config/init/systemd/Makefile.am| 10 + config/init/systemd/lxc-net.service.in |1 configure.ac |5 doc/api-extensions.md |9 + doc/ja/lxc.container.conf.sgml.in | 129 - doc/lxc.container.conf.sgml.in | 98 lxc.spec.in|1 meson.build|4 src/lxc/api_extensions.h |3 src/lxc/cgroups/cgfsng.c | 93 +++ src/lxc/cmd/lxc-checkconfig.in |6 - src/lxc/cmd/lxc_monitord.c | 59 + src/lxc/cmd/lxc_user_nic.c |2 src/lxc/conf.c | 11 + src/lxc/confile.c | 664 +--- src/lxc/network.c | 18 ++- src/lxc/network.h |4 src/lxc/terminal.c |1 src/lxc/terminal.h |3 src/lxc/tools/lxc_autostart.c |8 + src/lxc/utils.c|3 src/tests/aa.c |2 src/tests/config_jump_table.c |2 src/tests/containertests.c |2 src/tests/get_item.c | 90 ++- src/tests/getkeys.c|2 src/tests/locktests.c |2 src/tests/lxc-test-utils.c | 16 +- src/tests/meson.build | 534 ++ src/tests/mount_injection.c|2 src/tests/parse_config_file.c | 17 ++ src/tests/reboot.c |2 src/tests/share_ns.c |4 src/tests/snapshot.c |2 35 files changed, 1676 insertions(+), 134 deletions(-) ``` LXC 4.0.12 which we released on Feb 1st has all the bugfixes and other non-feature changes from LXC 5.0, making this quite a small and generally safe delta. The new features can be roughly categorized as: - Improve flexibility in cgroup configuration (make naming of /sys/fs/cgroup directories configurable) - Add support for the time namespace (clock offset) - Add support for configuring (basic sysctl) the number of veth queues - Add support for bridge VLAN filtering on veth devices LXC 5.0 will be an upstream LTS with a support duration matching that of Ubuntu 22.04 or until June 2027. Jammy currently ships LXC 4.0.12 which is only supported until June 2025 and will not see new bugfix releases after LXC 5.0 comes out (only security). LXC is unseeded and in universe these days. The main goal of putting the new LTS in the release is to reduce the maintenance cost for the Ubuntu LTS and to satisfy some of Canonical's customers that are directly using those packages and would expect a consistent set of LTS releases. LXCFS 5.0 is already in jammy and LXD 5.0 has similarly been released, though that one ships exclusively as a snap. If we can get general agreement that getting this LXC release in Ubuntu 22.04 is fine, what I can do to fast track things a bit is upload a 5.0~git-hash version which still relies on autotools, get that do clear autopkgtest and CI and then follow that up with the final 5.0 with the meson port as soon as it's complete on our side (expecting about a week, just got two directories to port). As a reminder, this is all unseeded and in universe, so overall impact should be quite low. Full upstream diff (4.0.12 to 5.0): https://gist.github.com/5c76aefcc8643e37a3e1b81a7a37a6f9 ** Affects: lxc (Ubuntu) Importance: High Status: New ** Changed in: lxc (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967620 Title: [FFe] LXC 5.0 LTS To manage notifications about this bug go to:
[Bug 1876979] Update Released
The verification of the Stable Release Update for lxd has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876979 Title: package lxd 3.0.3-0ubuntu1~18.04.1 failed to install/upgrade: new lxd package pre-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1876979/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964833] Update Released
The verification of the Stable Release Update for lxd has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964833 Title: Disable "latest" as upgrade option on focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1964833/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966499] Re: Recent 5.13 kernel has broken KVM support
Ah yeah, that could be. I figured I'd test what's in -proposed but if -proposed is a security only fix on top of -37, that wouldn't help much. It's a bit frustrating because users would have gotten the busted kernel as part of -37 which includes a security fix but then the only real option to get a booting system back now is to go to pre-security-fix. Unfortunately this is a production server and I already spent half of the week dealing with this mess so don't have more time to play kernel bingo. Server is now running a clean upstream build. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966499 Title: Recent 5.13 kernel has broken KVM support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966499/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966499] Re: Recent 5.13 kernel has broken KVM support
This repeats in a loop and fills tens of GBs of space with kernel logs in just a few minutes before crashing the entire system. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966499 Title: Recent 5.13 kernel has broken KVM support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966499/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966499] Re: Recent 5.13 kernel has broken KVM support
Mar 25 16:18:30 abydos kernel: [ 1319.549186] [ cut here ] Mar 25 16:18:30 abydos kernel: [ 1319.549191] WARNING: CPU: 12 PID: 15052 at arch/x86/kvm/vmx/vmx.c:6336 vmx_sync_pir_to_irr+0x9f/0xc0 [kvm_intel] Mar 25 16:18:30 abydos kernel: [ 1319.549213] Modules linked in: wireguard curve25519_x86_64 libchacha20poly1305 chacha_x86_64 poly1305_x86_64 libblake2s blake2s_x86_64 libcurve25519_generic libchacha libblake2s_generic xt_HL xt_MASQUERADE xt_TCPMSS xt_tcpudp binfmt_misc rbd unix_diag nf_conntrack_netlink veth ceph libceph fscache netfs zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) ebtable_filter ebtables ip6table_raw ip6table_mangle ip6table_nat ip6table_filter ip6_tables iptable_raw iptable_mangle iptable_nat iptable_filter bpfilter nf_tables vhost_vsock vmw_vsock_virtio_transport_common vhost vhost_iotlb vsock shiftfs sch_ingress geneve ip6_udp_tunnel udp_tunnel nfnetlink_cttimeout nfnetlink openvswitch nsh nf_conncount nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 8021q garp mrp nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_ssif intel_rapl_msr intel_rapl_common sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm rapl intel_cstate Mar 25 16:18:30 abydos kernel: [ 1319.549305] efi_pstore joydev input_leds cdc_acm mei_me mei ioatdma bridge stp llc bonding acpi_ipmi tls ipmi_si ipmi_devintf ipmi_msghandler acpi_power_meter acpi_pad mac_hid sch_fq_codel ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic usbhid hid ast drm_vram_helper drm_ttm_helper ttm drm_kms_helper syscopyarea sysfillrect sysimgblt crct10dif_pclmul fb_sys_fops crc32_pclmul ghash_clmulni_intel cec nvme rc_core aesni_intel crypto_simd ixgbe igb i2c_i801 xfrm_algo nvme_core drm i2c_smbus ahci i2c_algo_bit cryptd lpc_ich dca xhci_pci mdio libahci xhci_pci_renesas wmi Mar 25 16:18:30 abydos kernel: [ 1319.549394] CPU: 12 PID: 15052 Comm: qemu-system-x86 Tainted: P O 5.13.0-39-generic #44~20.04.1-Ubuntu Mar 25 16:18:30 abydos kernel: [ 1319.549399] Hardware name: Supermicro PIO-618U-T4T+-ST031/X10DRU-i+, BIOS 3.2a 11/19/2019 Mar 25 16:18:30 abydos kernel: [ 1319.549402] RIP: 0010:vmx_sync_pir_to_irr+0x9f/0xc0 [kvm_intel] Mar 25 16:18:30 abydos kernel: [ 1319.549415] Code: 83 c4 10 5b 5d c3 48 89 df e8 5d dc eb fd 8b 93 00 03 00 00 89 45 ec 83 e2 20 85 d2 75 d2 89 c7 e8 f6 fd ff ff 8b 45 ec eb c6 <0f> 0b eb 86 f0 80 4b 39 40 8b 93 00 03 00 00 8b 45 ec 83 e2 20 eb Mar 25 16:18:30 abydos kernel: [ 1319.549419] RSP: 0018:aed30c577cd8 EFLAGS: 00010246 Mar 25 16:18:30 abydos kernel: [ 1319.549423] RAX: RBX: 98162a4f8000 RCX: Mar 25 16:18:30 abydos kernel: [ 1319.549425] RDX: 0400 RSI: c0c38509 RDI: 98162a4f8000 Mar 25 16:18:30 abydos kernel: [ 1319.549428] RBP: aed30c577cf0 R08: 0400 R09: 98161e73fc00 Mar 25 16:18:30 abydos kernel: [ 1319.549430] R10: R11: R12: 98162a4f8000 Mar 25 16:18:30 abydos kernel: [ 1319.549433] R13: 7f272bff9dd0 R14: 98161e73fc00 R15: 98162a4f8000 Mar 25 16:18:30 abydos kernel: [ 1319.549435] FS: 7f272bffe700() GS:981c9f80() knlGS: Mar 25 16:18:30 abydos kernel: [ 1319.549439] CS: 0010 DS: ES: CR0: 80050033 Mar 25 16:18:30 abydos kernel: [ 1319.549442] CR2: 7f2a31708001 CR3: 0009ea4ac001 CR4: 001726e0 Mar 25 16:18:30 abydos kernel: [ 1319.549445] Call Trace: Mar 25 16:18:30 abydos kernel: [ 1319.549447] Mar 25 16:18:30 abydos kernel: [ 1319.549450] kvm_arch_vcpu_ioctl+0x8fd/0x1260 [kvm] Mar 25 16:18:30 abydos kernel: [ 1319.549590] ? kvm_arch_vcpu_ioctl+0xc1/0x1260 [kvm] Mar 25 16:18:30 abydos kernel: [ 1319.549659] ? kfree+0xd8/0x2a0 Mar 25 16:18:30 abydos kernel: [ 1319.549669] kvm_vcpu_ioctl+0x3a7/0x5f0 [kvm] Mar 25 16:18:30 abydos kernel: [ 1319.549720] ? __fget_light+0xce/0xf0 Mar 25 16:18:30 abydos kernel: [ 1319.549728] __x64_sys_ioctl+0x91/0xc0 Mar 25 16:18:30 abydos kernel: [ 1319.549734] do_syscall_64+0x61/0xb0 Mar 25 16:18:30 abydos kernel: [ 1319.549739] ? do_syscall_64+0x6e/0xb0 Mar 25 16:18:30 abydos kernel: [ 1319.549742] ? syscall_exit_to_user_mode+0x27/0x50 Mar 25 16:18:30 abydos kernel: [ 1319.549747] ? do_syscall_64+0x6e/0xb0 Mar 25 16:18:30 abydos kernel: [ 1319.549750] ? syscall_exit_to_user_mode+0x27/0x50 Mar 25 16:18:30 abydos kernel: [ 1319.549755] ? do_syscall_64+0x6e/0xb0 Mar 25 16:18:30 abydos kernel: [ 1319.549758] entry_SYSCALL_64_after_hwframe+0x44/0xae Mar 25 16:18:30 abydos kernel: [ 1319.549771] RIP: 0033:0x7f2a3b2b33db Mar 25 16:18:30 abydos kernel: [ 1319.549775] Code: 0f 1e fa 48 8b 05 b5 7a 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44
[Bug 1966499] [NEW] Recent 5.13 kernel has broken KVM support
Public bug reported: Upgrading to 5.13.0-37 or 5.13.0-39 immediately crashes my production servers as they hit: https://lore.kernel.org/all/f1ea22d3-cff8-406a-ad6a-cb8e0124a...@leemhuis.info/T/#md1f5c8c4aa01130a449a47f3e7559f06b0372f55 It looks like we need to get e90e51d5f01d included in those kernels. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966499 Title: Recent 5.13 kernel has broken KVM support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966499/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959047] Re: systemd ignores RootDirectory option in .service units
Uploaded to the queue ** Changed in: lxd (Ubuntu Bionic) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959047 Title: systemd ignores RootDirectory option in .service units To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1959047/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959047] Re: systemd ignores RootDirectory option in .service units
Okay, that looks promising. Can you add the SRU sections to the description describing those testing steps? Then I can upload to the SRU queue referencing this bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959047 Title: systemd ignores RootDirectory option in .service units To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1959047/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1935880] Re: lxc c2-m2 focal VM causes KVM internal error during PCI init
Adding linux-kvm to the bug. It looks like if we can have the commit above backported, it would take care of this issue for most users. ** Also affects: linux-kvm (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-kvm (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1935880 Title: lxc c2-m2 focal VM causes KVM internal error during PCI init To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1935880/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959047] Re: systemd ignores RootDirectory option in .service units
Uploading a LXD SRU to bionic with the one commit cherry-picked shouldn't be too hard. But we'd need someone to sort out the SRU paperwork as I have no idea how we'd even test the fix. ** Changed in: lxd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959047 Title: systemd ignores RootDirectory option in .service units To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1959047/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876979] Re: package lxd 3.0.3-0ubuntu1~18.04.1 failed to install/upgrade: new lxd package pre-installation script subprocess returned error exit status 1
Just tested this update with a running container and the upgrade went through correctly. It's hard to tell if this would have normally failed given that based on the output, shmounts and devlxd weren't mounted at the time things got purged but it at least shows that the potentially problematic case upgrades properly and that things didn't regress. ** Tags removed: focal verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876979 Title: package lxd 3.0.3-0ubuntu1~18.04.1 failed to install/upgrade: new lxd package pre-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1876979/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964833] Re: Disable "latest" as upgrade option on focal
Just tested this by running the new package on an Ubuntu 18.04 system with LXD 3.0 running (including one running instance). The prompt showed up as expected and indeed just offered 3.0 and 4.0 with 4.0 selected as default. Upgrade worked and container is still functional on the 4.0 snap. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964833 Title: Disable "latest" as upgrade option on focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1964833/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964636] Re: Incorrect handling of apparmor `bpf` capability
The warning message: """ Warning from stdin (line 1): apparmor_parser: Warning capping number of jobs to 0 * # of cpus == '16' """ Is caused by a LXCFS bug which we've since fixed. Systems still showing this message are in need of a snap refresh and host reboot. It's quite likely that the warning is somehow causing apparmor_parser to exit non-zero which would be the core of the issue here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964636 Title: Incorrect handling of apparmor `bpf` capability To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1964636/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965427] Re: [FFe] LXCFS 5.0 LTS
** Patch added: "lxcfs_5.0.0.debdiff" https://bugs.launchpad.net/ubuntu/+source/lxcfs/+bug/1965427/+attachment/5570157/+files/lxcfs_5.0.0.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965427 Title: [FFe] LXCFS 5.0 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxcfs/+bug/1965427/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965427] [NEW] [FFe] LXCFS 5.0 LTS
Public bug reported: LXCFS 5.0 LTS was released last week. The highlights of this is: - Switch to meson build system - Better detection and handling of CGroup2 - /proc/slabinfo support - /sys/devices/system/cpu support Of those, only the last two are user visible changes and just result in more files becoming CGroup-aware in the container. LXCFS 5.0 is an LTS release with 5 years support from upstream, that along with future-proofing through the cgroup2 improvement is the main reason why we'd like this to be in 22.04 LTS. LXCFS is in universe as its main user (LXD) uses an upstream build in a snap instead (already on 4.0). We nevertheless like to make sure that Ubuntu LTS releases include the deb form of the LXC and LXCFS LTS releases. We already have this version of LXCFS deployed to all LXD snap users and other than a few initial issues which are cherry-picked into the package, we've not seen any major issue. We are most likely to release a 5.0.1 bugfix release prior to final freeze for Ubuntu so we can do the final 22.04 release without the cherry-picks. ** Affects: lxcfs (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/1965427 Title: [FFe] LXCFS 5.0 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxcfs/+bug/1965427/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876979] Re: package lxd 3.0.3-0ubuntu1~18.04.1 failed to install/upgrade: new lxd package pre-installation script subprocess returned error exit status 1
** Description changed: running do-release-upgrade from ubuntu 18.04 to 20.04 i got this upgrade error for lxd ProblemType: Package DistroRelease: Ubuntu 20.04 Package: lxd 3.0.3-0ubuntu1~18.04.1 ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18 Uname: Linux 4.15.0-99-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 Date: Tue May 5 22:08:32 2020 EcryptfsInUse: Yes ErrorMessage: new lxd package pre-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: - dpkg 1.19.7ubuntu3 - apt 2.0.2 + dpkg 1.19.7ubuntu3 + apt 2.0.2 SourcePackage: lxd Title: package lxd 3.0.3-0ubuntu1~18.04.1 failed to install/upgrade: new lxd package pre-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-05-05 (0 days ago) modified.conffile..etc.apparmor.d.usr.lib.lxd.lxd-bridge-proxy: [deleted] modified.conffile..etc.dnsmasq.d-available.lxd: [deleted] modified.conffile..etc.init.d.lxd: [deleted] modified.conffile..etc.logrotate.d.lxd: [deleted] modified.conffile..etc.sysctl.d.10-lxd-inotify.conf: [deleted] + + + [Impact] + The migration script which transitions users from the deb to the snap completes the migration by deleting the old directory. In cases where we have mountpoints in there the migration fails. With this change, we attempt to unmount those paths (but not fail should they be missing). + + [Test plan] + Ideally, get a system which has both /var/lib/lxd/shmounts and /var/lib/lxd/devlxd mounted (should be possible if a container is running) and then upgrade, confirm that no error is shown at the end of the upgrade. + + [Where problems could occur] + Can't really think of anything, the two unmounts run with "|| true" so at worst they should behave the same as without. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876979 Title: package lxd 3.0.3-0ubuntu1~18.04.1 failed to install/upgrade: new lxd package pre-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1876979/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964833] Re: Disable "latest" as upgrade option on focal
lxd_0.10_source.changes uploaded to the queue -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964833 Title: Disable "latest" as upgrade option on focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1964833/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964833] Re: Disable "latest" as upgrade option on focal
Note that I'm not pushing for an impish version of this change as this package in impish is unused. The transitional "lxd" package is only relevant when upgrading from a pre-snap system which is only possible when upgrading from bionic to focal. The package has now been removed entirely from jammy, something we should have done a few releases ago. ** Description changed: The "lxd" transitional deb-to-snap package currently offers "3.0", "4.0" and "latest" as track options with "4.0" being the recommended and default one. Starting with LXD 5.0, it will no longer be possible to upgrade from LXD 3.0 without first going through LXD 4.0. As a result, the deb-to-snap logic in focal should be updated to remove "latest" as an option. Instead users will have to pick between "3.0" or "4.0" and can then upgrade afterwards by switching snap track. + The impact from this should be minimal as most users have already gone + through this process and those who haven't are likely to go with the + default option anyway (4.0). - The impact from this should be minimal as most users have already gone through this process and those who haven't are likely to go with the default option anyway (4.0). + [Impact] + LXD 5.0 (to be released end of March) will break the upgrade path when coming from a release prior to 4.0.0. + + The deb-to-snap logic in Ubuntu 20.04 currently offers "latest" as a + track for users switching to the snap (from 3.0 deb). This option will + start breaking once 5.0 is released and should be removed from the + upgrader prior to that. + + The users will lose the option to go straight to "latest" during the + deb-to-snap process instead being pushed towards "4.0" which they can + then upgrade from after the fact using "snap refresh". + + The "4.0" track was already the default and used by virtually all users + to date, so the change is unlikely to be particularly visible. + + [Test plan] + Get an Ubuntu 18.04 system, run "lxd init --auto" to initialize LXD, then upgrade to 20.04 and confirm that the debconf prompt defaults to "4.0" and does not offer "latest" as a track option. + + [Where problems could occur] + If this SRU isn't in focal-updates by the time LXD 5.0 releases to latest/stable (first week of April), some users may chose "latest" during the upgrade which will fail and fail the LTS-to-LTS process giving them a hard to recover system. ** Changed in: lxd (Ubuntu) Status: New => Fix Committed ** Changed in: lxd (Ubuntu) Status: Fix Committed => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964833 Title: Disable "latest" as upgrade option on focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1964833/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964833] [NEW] Disable "latest" as upgrade option on focal
Public bug reported: The "lxd" transitional deb-to-snap package currently offers "3.0", "4.0" and "latest" as track options with "4.0" being the recommended and default one. Starting with LXD 5.0, it will no longer be possible to upgrade from LXD 3.0 without first going through LXD 4.0. As a result, the deb-to-snap logic in focal should be updated to remove "latest" as an option. Instead users will have to pick between "3.0" or "4.0" and can then upgrade afterwards by switching snap track. The impact from this should be minimal as most users have already gone through this process and those who haven't are likely to go with the default option anyway (4.0). [Impact] LXD 5.0 (to be released end of March) will break the upgrade path when coming from a release prior to 4.0.0. The deb-to-snap logic in Ubuntu 20.04 currently offers "latest" as a track for users switching to the snap (from 3.0 deb). This option will start breaking once 5.0 is released and should be removed from the upgrader prior to that. The users will lose the option to go straight to "latest" during the deb-to-snap process instead being pushed towards "4.0" which they can then upgrade from after the fact using "snap refresh". The "4.0" track was already the default and used by virtually all users to date, so the change is unlikely to be particularly visible. [Test plan] Get an Ubuntu 18.04 system, run "lxd init --auto" to initialize LXD, then upgrade to 20.04 and confirm that the debconf prompt defaults to "4.0" and does not offer "latest" as a track option. [Where problems could occur] If this SRU isn't in focal-updates by the time LXD 5.0 releases to latest/stable (first week of April), some users may chose "latest" during the upgrade which will fail and fail the LTS-to-LTS process giving them a hard to recover system. ** Affects: lxd (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/1964833 Title: Disable "latest" as upgrade option on focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1964833/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964786] Re: [FFe] Remove deb to snap transitional package
Removing packages from jammy: lxd 1:0.9 in jammy lxd 1:0.9 in jammy amd64 lxd 1:0.9 in jammy arm64 lxd 1:0.9 in jammy armhf lxd 1:0.9 in jammy i386 lxd 1:0.9 in jammy ppc64el lxd 1:0.9 in jammy riscv64 lxd 1:0.9 in jammy s390x lxd-client 1:0.9 in jammy amd64 lxd-client 1:0.9 in jammy arm64 lxd-client 1:0.9 in jammy armhf lxd-client 1:0.9 in jammy i386 lxd-client 1:0.9 in jammy ppc64el lxd-client 1:0.9 in jammy riscv64 lxd-client 1:0.9 in jammy s390x lxd-tools 1:0.9 in jammy amd64 lxd-tools 1:0.9 in jammy arm64 lxd-tools 1:0.9 in jammy armhf lxd-tools 1:0.9 in jammy i386 lxd-tools 1:0.9 in jammy ppc64el lxd-tools 1:0.9 in jammy riscv64 lxd-tools 1:0.9 in jammy s390x adapt 1.5-0ubuntu1 in jammy adapt 1.5-0ubuntu1 in jammy amd64 adapt 1.5-0ubuntu1 in jammy arm64 adapt 1.5-0ubuntu1 in jammy armhf adapt 1.5-0ubuntu1 in jammy i386 adapt 1.5-0ubuntu1 in jammy ppc64el adapt 1.5-0ubuntu1 in jammy riscv64 adapt 1.5-0ubuntu1 in jammy s390x Comment: LP: #1964786 Remove [y|N]? y 2 packages successfully removed. ** Changed in: adapt (Ubuntu) Status: Confirmed => Fix Released ** Changed in: lxd (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964786 Title: [FFe] Remove deb to snap transitional package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adapt/+bug/1964786/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964786] Re: [FFe] Remove deb to snap transitional package
Basically `adapt` expects that `images.linuxcontainers.org` is a LXD- protocol server, it doesn't know about our transition to simplestreams starting at around LXD 2.0.4 (August 2016) and those image servers have not actually supported that older API for a long time now. ** Changed in: adapt (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964786 Title: [FFe] Remove deb to snap transitional package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adapt/+bug/1964786/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964786] Re: [FFe] Remove deb to snap transitional package
The `adapt` package has been broken since at least 2016 as it hardcodes an image server path and patterns that haven't been valid for years. As a result, it's impossible for anyone to have successfully used adapt on Ubuntu since pre-16.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964786 Title: [FFe] Remove deb to snap transitional package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adapt/+bug/1964786/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964786] [NEW] [FFe] Remove deb to snap transitional package
Public bug reported: The `lxd` package (`lxd`, `lxd-client`, `lxd-tools`) has been replaced by a snap starting with Ubuntu 18.10. To facilitate that, the main `lxd` package was turned into an automatic conversion package which on install will trigger the installation of the snap and migration of the data from the deb to the snap. It also accidentally served the role of having a deb package which would pull in the lxd snap. As this package didn't really serve much of a purpose after the 18.04 to 20.04 upgrade handling, it should be removed from the archive and not make it into another LTS release. Looking at its rdepends, we have: - adapt (depends) - autopkgtest (suggests) - lxd-installer (conflicts) Of those only `adapt` needs something done to handle this change. Looking at `adapt`, it's been broken for many many years, due to using a deprecated image server for LXD. As a result, I don't believe anyone could have used it since around the 16.04 times. My suggestion here is that we do: - Delete adapt from the archive - Delete lxd from the archive I'm marking this as a Feature Freeze Exception as two packages would go away from the archive, but neither are actually useful today so there should be no actual user visible impact from this. ** Affects: adapt (Ubuntu) Importance: Undecided Status: New ** Affects: lxd (Ubuntu) Importance: Undecided Status: New ** Also affects: adapt (Ubuntu) Importance: Undecided Status: New ** Summary changed: - [FFE] Remove deb to snap transitional package + [FFe] Remove deb to snap transitional package -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964786 Title: [FFe] Remove deb to snap transitional package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adapt/+bug/1964786/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964723] Re: [FFE] lttng-modules is out of sync with lttng-tools
This bug was fixed in the package lttng-modules - 2.13.1-1 Sponsored for Michael Jeanson (mjeanson) --- lttng-modules (2.13.1-1) unstable; urgency=medium * [a4701a4] New upstream version 2.13.1 -- Michael Jeanson Wed, 05 Jan 2022 14:08:28 -0500 lttng-modules (2.13.0-2) unstable; urgency=medium * [6d6009d] Update Salsa CI pipeline config * [9c934f8] Update to debhelper compat 12 -- Michael Jeanson Fri, 22 Oct 2021 12:08:28 -0400 lttng-modules (2.13.0-1) unstable; urgency=medium * [d3af6a6] New upstream version 2.13.0 * [917bbe8] Refreshed patches for 2.13 * [cf4c5cb] Bump watch file version to 4 * [1902e3b] Update debian/copyright * [049e5c3] Exclude new docs from dkms package * [219cd42] Update dkms config -- Michael Jeanson Mon, 18 Oct 2021 15:45:42 -0400 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964723 Title: [FFE] lttng-modules is out of sync with lttng-tools To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lttng-modules/+bug/1964723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964723] Re: [FFE] lttng-modules is out of sync with lttng-tools
Approving this FFe with my ubuntu-release hat on, the new features are fine especially as the userspace side is already present and the fact that things aren't lined up currently is a bit of an issue. ** Summary changed: - lttng-modules is out of sync with lttng-tools + [FFE] lttng-modules is out of sync with lttng-tools ** Changed in: lttng-modules (Ubuntu) Status: New => Triaged ** Changed in: lttng-modules (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964723 Title: [FFE] lttng-modules is out of sync with lttng-tools To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lttng-modules/+bug/1964723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964636] Re: Incorrect handling of apparmor `bpf` capability
@jjohansen nope, we use the apparmor_parser that ships in core20. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964636 Title: Incorrect handling of apparmor `bpf` capability To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1964636/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964636] Re: Incorrect handling of apparmor `bpf` capability
Yeah, that's because you're using LXD 4.23 which has the older LXCFS and doesn't trigger the apparmor warning message which then confuses everything else (per previous comment). If you `snap install lxd --channel=latest/edge`, you should start getting the broken behavior. Note however that we did fix LXCFS so that broken behavior on an apparmor warning will soon go away as the warning in question will no longer be issued by apparmor. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964636 Title: Incorrect handling of apparmor `bpf` capability To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1964636/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964636] Re: Incorrect handling of apparmor `bpf` capability
As part of digging into this issue, I found this error: ``` Warning from stdin (line 1): apparmor_parser: Warning capping number of jobs to 0 * # of cpus == '4' ``` Which started appearing since we released LXCFS 5.0.0 (available in LXD edge and candidate). The root cause is https://github.com/lxc/lxcfs/issues/522 This only causes an apparmor warning and the parser is otherwise functional, but this may also be interacting with snapd somehow, causing it to mis-detect available or missing features somehow? ** Bug watch added: LXCFS bug tracker #522 https://github.com/lxc/lxcfs/issues/522 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964636 Title: Incorrect handling of apparmor `bpf` capability To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1964636/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964636] Re: Incorrect handling of apparmor `bpf` capability
The steps in the description reproduce this issue for me on a clean Ubuntu 20.04 server install on either 5.4.0 (GA) or 5.13.0 (HWE) kernels. The container doesn't need to be privileged. The main steps really seem to be the installation of a classic snap followed by restart of the container. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964636 Title: Incorrect handling of apparmor `bpf` capability To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1964636/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964636] [NEW] Incorrect handling of apparmor `bpf` capability
Public bug reported:
We've recently noticed a lot of the LXD CI jobs failing because of
apparmor related snapd issues.
The way this usually manifests is:
- lxc launch images:ubuntu/20.04 c1
- lxc exec c1 -- apt install snapd
- lxc exec c1 -- snap install distrobuilder --edge --classic
- lxc exec c1 -- distrobuilder
This all works as expected, `systemctl --failed` is clean and `apparmor_status`
gets me:
```
0 loaded units listed.
root@v1:~# lxc exec c1 -- apparmor_status
apparmor module is loaded.
11 profiles are loaded.
10 profiles are in enforce mode.
/usr/lib/NetworkManager/nm-dhcp-client.action
/usr/lib/NetworkManager/nm-dhcp-helper
/usr/lib/connman/scripts/dhclient-script
/usr/lib/snapd/snap-confine
/usr/lib/snapd/snap-confine//mount-namespace-capture-helper
/{,usr/}sbin/dhclient
lsb_release
nvidia_modprobe
nvidia_modprobe//kmod
snap-update-ns.distrobuilder
1 profiles are in complain mode.
snap.distrobuilder.distrobuilder
0 processes have profiles defined.
0 processes are in enforce mode.
0 processes are in complain mode.
0 processes are unconfined but have a profile defined.
```
Now to break things:
- lxc restart c1
- lxc exec c1 -- distrobuilder
```
root@v1:~# lxc exec c1 -- distrobuilder
cannot change profile for the next exec call: No such file or directory
```
Looking around, we see:
```
root@c1:~# find /var/lib/snapd/apparmor/
/var/lib/snapd/apparmor/
/var/lib/snapd/apparmor/snap-confine
/var/lib/snapd/apparmor/snap-confine/cap-bpf
/var/lib/snapd/apparmor/profiles
/var/lib/snapd/apparmor/profiles/snap.distrobuilder.distrobuilder
/var/lib/snapd/apparmor/profiles/snap-update-ns.distrobuilder
/var/lib/snapd/apparmor/profiles/snap-confine.snapd.14978
root@c1:~# cat /var/lib/snapd/apparmor/snap-confine/cap-bpf
capability bpf,
root@c1:~# systemctl --failed
UNIT LOAD ACTIVE SUBDESCRIPTION
● snapd.apparmor.service loaded failed failed Load AppArmor profiles managed
internally by snapd
LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB= The low-level unit activation state, values depend on unit type.
1 loaded units listed.
```
The error listed is:
```
Mar 11 19:54:58 c1 systemd[1]: Starting Load AppArmor profiles managed
internally by snapd...
Mar 11 19:54:58 c1 snapd-apparmor[163]: /usr/lib/snapd/snapd-apparmor: 47:
ns_stacked: not found
Mar 11 19:54:58 c1 snapd-apparmor[163]: /usr/lib/snapd/snapd-apparmor: 48:
ns_name: not found
Mar 11 19:54:58 c1 snapd-apparmor[172]: AppArmor parser error for
/var/lib/snapd/apparmor/profiles/snap-confine.snapd.14978 in
/var/lib/snapd/apparmor/snap-confine/cap-bpf at line 2: Invalid capability bpf.
Mar 11 19:54:58 c1 systemd[1]: snapd.apparmor.service: Main process exited,
code=exited, st
```
One can workaround it with:
```
> /var/lib/snapd/apparmor/snap-confine/cap-bpf
systemctl restart snapd.apparmor.service
```
Now for the bits I didn't quite figure out:
- Why does snapd think that the parser supports `bpf` when it in fact doesn't?
- Why does this only seem to hit with `distrobuilder`, testing with
`hello-world` doesn't hit this issue though we've seen similar behavior from
the `go` snap, is it a bug that only triggers on classic snaps?
** Affects: snapd (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/1964636
Title:
Incorrect handling of apparmor `bpf` capability
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1964636/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959993] Re: SRU of LXC 4.0.12 to focal (upstream bugfix release)
Uploaded the exact same thing to impish queue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959993 Title: SRU of LXC 4.0.12 to focal (upstream bugfix release) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1959993/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959993] Re: SRU of LXC 4.0.12 to focal (upstream bugfix release)
Thanks Brian, my memory of this whole thing clearly dates back a long time then ;) I still remember some of the discussions of what we'd expect people to be doing in such cases and whether we'd ever officially support (as in test/validate) upgrade paths other than release to release+1 and LTS to LTS+1. I remember us struggling to really validate those two more common paths so I wonder what's done today to validate the upgrade paths when one release goes EOL and the upgrade path changes to something different for those upgrading from the LTS. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959993 Title: SRU of LXC 4.0.12 to focal (upstream bugfix release) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1959993/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960847] Re: lxc autopkgtests failures with cgroupv2 on jammy
Marking this invalid against LXC as the code in the archive for package testing is handling this case properly already. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960847 Title: lxc autopkgtests failures with cgroupv2 on jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1960847/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960847] Re: lxc autopkgtests failures with cgroupv2 on jammy
The autopkgtest script in the Ubuntu package has: # Skip some tests due to cgroup v2 incompatibility if [ -e /sys/fs/cgroup/system.slice/memory.current ]; then [ "$testbin" = "lxc-test-apparmor-mount" ] && \ ignore "$STRING" && continue [ "$testbin" = "lxc-test-autostart" ] && \ ignore "$STRING" && continue [ "$testbin" = "lxc-test-no-new-privs" ] && \ ignore "$STRING" && continue [ "$testbin" = "lxc-test-unpriv" ] && \ ignore "$STRING" && continue fi And it did clear autopkgtest very recently in jammy. Closing this issue. I think a lot of the recent issues we've been getting with kernel testing of LXC is because you're not actually running the same autopkgtest and packages that we are in the main archive. This caused library/binary mismatches in a recent issue and now is causing issues because of the difference in test script (the on in lxc- ci is lagging behind in this case which isn't a problem as the LXC CI environment runs hybrid cgroupv1 on purpose). ** Changed in: lxc (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960847 Title: lxc autopkgtests failures with cgroupv2 on jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1960847/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959993] Re: SRU of LXC 4.0.12 to focal (upstream bugfix release)
(We technically had the same issue with the previous upload as 4.0.6 was higher than what hirsute shipped at the time, though in that case the EOL for hirsute was just a month or so away making the case for skipping that SRU even stronger :)) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959993 Title: SRU of LXC 4.0.12 to focal (upstream bugfix release) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1959993/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959993] Re: SRU of LXC 4.0.12 to focal (upstream bugfix release)
In general, it's indeed a problem for such cases, though there are a few mitigating factors here: - This would only be a problem for those who upgrade from focal to impish. My understanding is that there is no direct upgrade path to achieve this, you'd need to go throughgroovy and hirsute, both of which are EOL, so I wouldn't really expect many/any user to do this. - The LXC team is responsible for self-assigning CVEs and preparing LXC security updates (~ubuntu-lxc-security). In such cases we usually prefer releasing a new upstream bugfix release (LXC 4.0.x is an LTS with a 5 years security commitment upstream) and then upload that to the -security pockets where applicable. So in that case, we'd bump jammy to match focal, saving us some effort on validating the security update by making things be identical on all releases shipping 4.0.x (jammy will be on 5.0.x). That's generally how we've handled those micro release updates and so far haven't run into any problems but I'm also not necessarily against uploading the exact same source package as focal to impish, the preparation time would be pretty minimal, it's mostly on the review and testing side of things that things can increase significantly especially as we usually struggle to find users on non-LTS to perform more than a simple install/upgrade test. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959993 Title: SRU of LXC 4.0.12 to focal (upstream bugfix release) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1959993/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960094] Re: lxc/1:4.0.6-0ubuntu1~20.04.1 undefined symbol: strlcat in Focal
Closing the LXC task for now as that seems to be unrelated to a LXC change (we haven't uploaded in a while) and not related to a new kernel release which could actually cause such a change. If you track this down to something other than an issue in your test environment, please add lxc to this issue again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960094 Title: lxc/1:4.0.6-0ubuntu1~20.04.1 undefined symbol: strlcat in Focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960094/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960094] Re: lxc/1:4.0.6-0ubuntu1~20.04.1 undefined symbol: strlcat in Focal
** Changed in: lxc (Ubuntu) Status: Incomplete => Invalid ** Changed in: lxc (Ubuntu Focal) Status: Incomplete => Invalid ** No longer affects: lxc (Ubuntu) ** No longer affects: lxc (Ubuntu Focal) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960094 Title: lxc/1:4.0.6-0ubuntu1~20.04.1 undefined symbol: strlcat in Focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960094/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960094] Re: lxc/1:4.0.6-0ubuntu1~20.04.1 undefined symbol: strlcat in Focal
I think the strlcat thing is a red herring or an indication that the test environment is somehow in a bad shape. This could be explained if there was two versions of liblxc on the system for example. Outside of that, I'm also seeing: ``` lxc-start tmp.KEpxw2rh0e 20220205081512.354 ERRORutils - utils.c:__safe_mount_beneath_at:1106 - Function not implemented - Failed to open 30(full) ``` Which isn't a test issue but an actual failure. It could once again come from a bad test environment with mismatching library/binary somehow, but if the test environment isn't the issue, then you have a kernel regression on your hands as that's not one of those transient test failures. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960094 Title: lxc/1:4.0.6-0ubuntu1~20.04.1 undefined symbol: strlcat in Focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960094/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960094] Re: lxc/1:4.0.12-0ubuntu1~20.04.1 undefined symbol: strlcat in Focal
Hmm, hold on, this makes no sense. You're reporting this against focal, but 4.0.12-0ubuntu1 is the jammy version of lxc, so what's going on here exactly? Also, all the links posted are unreachable, please avoid internal links and attach the logs instead. ** Changed in: lxc (Ubuntu) Status: New => Incomplete ** Changed in: lxc (Ubuntu Focal) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960094 Title: lxc/1:4.0.12-0ubuntu1~20.04.1 undefined symbol: strlcat in Focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960094/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959993] Re: SRU of LXC 4.0.12 to focal (upstream bugfix release)
Worth noting that with this upload, the packaging gets virtually in sync with jammy minus a few artifacts of git-dpm in the patches, this should make maintenance a fair bit easier should a follow-up SRU be needed. Upstream packaging delta: https://github.com/lxc/lxc-pkg-ubuntu/compare/debian/1%254.0.6-0ubuntu1_20.04.1...debian/1%254.0.12-0ubuntu1_20.04.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959993 Title: SRU of LXC 4.0.12 to focal (upstream bugfix release) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1959993/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959993] Re: SRU of LXC 4.0.12 to focal (upstream bugfix release)
Source package and all resulting binary packages are "lintian -iI" clean except for the warning caused by SRU version numbering. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959993 Title: SRU of LXC 4.0.12 to focal (upstream bugfix release) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1959993/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959993] Re: SRU of LXC 4.0.12 to focal (upstream bugfix release)
Uploaded to focal SRU queue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959993 Title: SRU of LXC 4.0.12 to focal (upstream bugfix release) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1959993/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959993] Re: SRU of LXC 4.0.12 to focal (upstream bugfix release)
A build of the proposed SRU is available for all architectures (well, riscv64 is slowly building) at: https://launchpad.net/~stgraber/+archive/ubuntu/experimental-devirt/ ** Description changed: - LXC released 4.0.12 as a bugfix release and is now in jammy. We'd like to line things up in focal. + LXC released 4.0.12 as a bugfix release and is now in jammy. We'd like + to line things up in focal. + + [Impact] The proposed SRU will bump from 4.0.6 all the way to 4.0.12, lining it up with what's currently in jammy. We've been skipping a few of the bugfix releases in focal so far, mostly catching up when we're starting to see problems with the older version. In this case, we've seen a number of issues when running with the HWE kernels as well as autopkgtest issues on foreign architectures (arm64 and s390x), all those will go away with this bump as we've confirmed everything is clean in jammy. - Changelog: + * Cherry-pick upstream bugfixes (stable-4.0): + - 0002-lxc-checkconfig-Fix-bashism.patch + - 0003-doc-Fix-reverse-allowlist-denylist.patch - * Cherry-pick upstream bugfixes (stable-4.0): - - 0002-lxc-checkconfig-Fix-bashism.patch - - 0003-doc-Fix-reverse-allowlist-denylist.patch + * New upstream bugfix release (4.0.12): + (https://discuss.linuxcontainers.org/t/lxc-4-0-12-has-been-released/13288) + - Fixed CRIU restoration of containers with pre-created veth interfaces + - Fixed issue with kernels lacking SMT support + - Extended cgroup2 config options in lxc.mount.auto (cgroup2) + - lxc-download now relies on HTTPS for validation (avoids GPG issues) - * New upstream bugfix release (4.0.12): - (https://discuss.linuxcontainers.org/t/lxc-4-0-12-has-been-released/13288) - - Fixed CRIU restoration of containers with pre-created veth interfaces - - Fixed issue with kernels lacking SMT support - - Extended cgroup2 config options in lxc.mount.auto (cgroup2) - - lxc-download now relies on HTTPS for validation (avoids GPG issues) + * New upstream bugfix release (4.0.11): + (https://discuss.linuxcontainers.org/t/lxc-4-0-11-has-been-released/12427) + - Core scheduling support (lxc.sched.core) + - riscv64 support in lxc.arch + - Significantly improved bash completion profile + - Greater use of the new VFS mount API (when supported by the kernel) + - Fix containers with empty network namespaces + - Handle kernels that lack TIOCGPTPEER + - Improve CPU bitmask/id handling (handle skipped CPU numbers) + - Reworked the tests to run offline - * New upstream bugfix release (4.0.11): - (https://discuss.linuxcontainers.org/t/lxc-4-0-11-has-been-released/12427) - - Core scheduling support (lxc.sched.core) - - riscv64 support in lxc.arch - - Significantly improved bash completion profile - - Greater use of the new VFS mount API (when supported by the kernel) - - Fix containers with empty network namespaces - - Handle kernels that lack TIOCGPTPEER - - Improve CPU bitmask/id handling (handle skipped CPU numbers) - - Reworked the tests to run offline + * New upstream bugfix release (4.0.10): + (https://discuss.linuxcontainers.org/t/lxc-4-0-10-has-been-released/11618) + - Fix issues with less common architectures + - Support for additional idmap mounts + - nft support in lxc-net + - Cleaner mount entries for sys:mixed + - Switched GPG server to keyserver.ubuntu.com - * New upstream bugfix release (4.0.10): - (https://discuss.linuxcontainers.org/t/lxc-4-0-10-has-been-released/11618) - - Fix issues with less common architectures - - Support for additional idmap mounts - - nft support in lxc-net - - Cleaner mount entries for sys:mixed - - Switched GPG server to keyserver.ubuntu.com + * New upstream bugfix release (4.0.9): + (https://discuss.linuxcontainers.org/t/lxc-4-0-9-has-been-released/10999) + - Fix incorrect personality setting when running 32bit containers on 64bit - * New upstream bugfix release (4.0.9): - (https://discuss.linuxcontainers.org/t/lxc-4-0-9-has-been-released/10999) - - Fix incorrect personality setting when running 32bit containers on 64bit + * New upstream bugfix release (4.0.8): + - Fix CGroup attach against older running containers - * New upstream bugfix release (4.0.8): - - Fix CGroup attach against older running containers + * New upstream bugfix release (4.0.7): + - Testing improvements including fixes from oss-fuzz + - Rework of the attach codepath + - Cgroup handling rework - * New upstream bugfix release (4.0.7): - - Testing improvements including fixes from oss-fuzz - - Rework of the attach codepath - - Cgroup handling rework - - * Bump to debhelper 12 (allows focal SRUs) - * Bump standards to 4.6.0.1 - * Add lintian overrides for incorrect bashism detection - * Remove bash completion install logic
[Bug 1959993] [NEW] SRU of LXC 4.0.12 to focal (upstream bugfix release)
Public bug reported: LXC released 4.0.12 as a bugfix release and is now in jammy. We'd like to line things up in focal. The proposed SRU will bump from 4.0.6 all the way to 4.0.12, lining it up with what's currently in jammy. We've been skipping a few of the bugfix releases in focal so far, mostly catching up when we're starting to see problems with the older version. In this case, we've seen a number of issues when running with the HWE kernels as well as autopkgtest issues on foreign architectures (arm64 and s390x), all those will go away with this bump as we've confirmed everything is clean in jammy. Changelog: * Cherry-pick upstream bugfixes (stable-4.0): - 0002-lxc-checkconfig-Fix-bashism.patch - 0003-doc-Fix-reverse-allowlist-denylist.patch * New upstream bugfix release (4.0.12): (https://discuss.linuxcontainers.org/t/lxc-4-0-12-has-been-released/13288) - Fixed CRIU restoration of containers with pre-created veth interfaces - Fixed issue with kernels lacking SMT support - Extended cgroup2 config options in lxc.mount.auto (cgroup2) - lxc-download now relies on HTTPS for validation (avoids GPG issues) * New upstream bugfix release (4.0.11): (https://discuss.linuxcontainers.org/t/lxc-4-0-11-has-been-released/12427) - Core scheduling support (lxc.sched.core) - riscv64 support in lxc.arch - Significantly improved bash completion profile - Greater use of the new VFS mount API (when supported by the kernel) - Fix containers with empty network namespaces - Handle kernels that lack TIOCGPTPEER - Improve CPU bitmask/id handling (handle skipped CPU numbers) - Reworked the tests to run offline * New upstream bugfix release (4.0.10): (https://discuss.linuxcontainers.org/t/lxc-4-0-10-has-been-released/11618) - Fix issues with less common architectures - Support for additional idmap mounts - nft support in lxc-net - Cleaner mount entries for sys:mixed - Switched GPG server to keyserver.ubuntu.com * New upstream bugfix release (4.0.9): (https://discuss.linuxcontainers.org/t/lxc-4-0-9-has-been-released/10999) - Fix incorrect personality setting when running 32bit containers on 64bit * New upstream bugfix release (4.0.8): - Fix CGroup attach against older running containers * New upstream bugfix release (4.0.7): - Testing improvements including fixes from oss-fuzz - Rework of the attach codepath - Cgroup handling rework * Bump to debhelper 12 (allows focal SRUs) * Bump standards to 4.6.0.1 * Add lintian overrides for incorrect bashism detection * Remove bash completion install logic (now done upstream) Just like Ubuntu itself, upstream releases long term support releases, e.g. 4.0, and then periodic point releases including all the accumulated bugfixes. Only the latest upstream release gets full support from the upstream developers, everyone else is expected to first update to it before receiving any kind of support. This should qualify under the minor/micro upstream bugfix release allowance of the SRU policy, letting us SRU this without paperwork for every single change included in this upstream release. [Test case] lxc has autopkgtests which will assert that the binaries built in -proposed are functional. ** Affects: lxc (Ubuntu) Importance: Undecided Assignee: Stéphane Graber (stgraber) Status: Triaged ** Changed in: lxc (Ubuntu) Status: New => Triaged ** Changed in: lxc (Ubuntu) Assignee: (unassigned) => Stéphane Graber (stgraber) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959993 Title: SRU of LXC 4.0.12 to focal (upstream bugfix release) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1959993/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1502604] Re: autopkgtests fail in LXC testbed
** Changed in: lxc (Ubuntu) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1502604 Title: autopkgtests fail in LXC testbed To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/1502604/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1510108] Re: pre-installed lxc in cloud-image means loss of access to 10.0.X.0/24
Closing as these days we only have LXD preinstalled on those images and LXD does a lot more validation and only creates the networks on first use. ** Changed in: lxc (Ubuntu) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1510108 Title: pre-installed lxc in cloud-image means loss of access to 10.0.X.0/24 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1510108/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1591124] Re: LXC: Cannot create a container with the specific alias "tasks"
** Changed in: lxc (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1591124 Title: LXC: Cannot create a container with the specific alias "tasks" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1591124/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1226855] Re: Cannot use open-iscsi inside LXC container
Closing the LXC side of this bug as there's nothing we can really do here. It's either a kernel issue (needs support for their socket option within a network namespace) or an open-iscsi issue where they could have some kind of fallback mechanism. ** Changed in: lxc (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1226855 Title: Cannot use open-iscsi inside LXC container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1226855/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1522992] Re: /usr/bin/lxc-stop:11:strlen:prune_init_scope:try_get_abs_cgroup:do_cgm_get:cgm_get
** Changed in: lxc (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1522992 Title: /usr/bin/lxc- stop:11:strlen:prune_init_scope:try_get_abs_cgroup:do_cgm_get:cgm_get To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1522992/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1303756] Re: make lxc-console work non-confusingly by default on touch images
Ubuntu Touch hasn't been a thing for a few years and UBPorts hasn't really been hitting this issue as far as I know. ** Changed in: lxc (Ubuntu) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1303756 Title: make lxc-console work non-confusingly by default on touch images To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1303756/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1515615] Re: Disk quotas don't work in LXC containers
@brauner do you know what's the state of quotas in a VFS idmapped shifted world? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1515615 Title: Disk quotas don't work in LXC containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1515615/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1549391] Re: /proc/sched_debug Information Leak
Closing as it's not really LXC's job to try and change that one. These days we'd recommend distros to change default permissions or ideally get that changed at the kernel level. Short of that, we do have some documented recommendations in our production environment doc for LXD: https://linuxcontainers.org/lxd/docs/master/production-setup/ ** Changed in: lxc (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1549391 Title: /proc/sched_debug Information Leak To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1549391/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1642767] Re: starting any container with umask 007 breaks host system shutdown. lxc-stop just hangs.
Moving over to the kernel as a userspace process shouldn't be able to cause such a hang regardless of what it does so this looks like a kernel bug (lock related by the looks of it). ** Package changed: lxc (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1642767 Title: starting any container with umask 007 breaks host system shutdown. lxc-stop just hangs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1642767/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1646462] Re: lxc-create cannot setgid
** Changed in: lxc (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1646462 Title: lxc-create cannot setgid To manage notifications about this bug go to: https://bugs.launchpad.net/lxc/+bug/1646462/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813362] Re: lxc-top flash error and blkio write is always zero
Could you recheck with the current LXC (4.0.12) as the cgroup code was reworked quite extensively. ** Changed in: lxc (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813362 Title: lxc-top flash error and blkio write is always zero To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1813362/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857542] Re: lxc-checkpoint needs the criu package
CRIU is once again in the archive (Ubuntu is just following what's in Debian for this one). ** Changed in: lxc (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1857542 Title: lxc-checkpoint needs the criu package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1857542/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881292] Re: Linux 5.7: autopkgtest failures - lxc-test-cloneconfig && lxc-destroy
Did we ever see this one again or was it just transient? ** Changed in: lxc (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881292 Title: Linux 5.7: autopkgtest failures - lxc-test-cloneconfig && lxc-destroy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1881292/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883041] Re: libpam-cgfs fails to create freezer cgroup writable by user
** Changed in: lxc (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1883041 Title: libpam-cgfs fails to create freezer cgroup writable by user To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1883041/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886790] Re: lxc 3.0.3-0ubuntu1~18.04.1 ADT test failure with B/5.4 kernels (device_add_remove_test)
** Changed in: lxc (Ubuntu) Status: In Progress => Fix Released ** Changed in: lxc (Ubuntu Bionic) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886790 Title: lxc 3.0.3-0ubuntu1~18.04.1 ADT test failure with B/5.4 kernels (device_add_remove_test) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1886790/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887919] Re: autopkgtest failure with libselinux 3.1
** Changed in: lxc (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887919 Title: autopkgtest failure with libselinux 3.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1887919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907307] Re: lxc 1:4.0.4-0ubuntu3 ADT test failure with linux 5.10.0-7.8
Are we still seeing this? The failure looks a lot like it could be a legitimate kernel issue. ** Changed in: lxc (Ubuntu) Status: New => Incomplete ** Changed in: lxc (Ubuntu Focal) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907307 Title: lxc 1:4.0.4-0ubuntu3 ADT test failure with linux 5.10.0-7.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1907307/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947811] Re: cgroups broken in impish
Said change is in LXCFS 4.0.12 which is now in jammy ** Changed in: lxcfs (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947811 Title: cgroups broken in impish To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxcfs/+bug/1947811/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1532314] Re: Buffer overflow in cgmanager
** Changed in: lxc (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: libnih (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1532314 Title: Buffer overflow in cgmanager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1532314/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916669] Re: autopkgtests flaky for hirsute across various architectures
Seems green lately ** Changed in: lxc (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916669 Title: autopkgtests flaky for hirsute across various architectures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1916669/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917187] Re: lxc cgroup2: containers unbootable
The error you're getting is coming from systemd in the container which for some reason is trying to mount a cgroup1 hierarchy rather than using cgroup2 like the rest of your system. You may be able to workaround that by using `lxc.init_cmd` to pass /sbin/init with additional arguments to change the systemd behavior in the container. ** Changed in: lxc (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917187 Title: lxc cgroup2: containers unbootable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1917187/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917601] Re: lxc 1:4.0.4-0ubuntu3 ADT test failure with linux 5.8.0-45.51
** Changed in: lxc (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917601 Title: lxc 1:4.0.4-0ubuntu3 ADT test failure with linux 5.8.0-45.51 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1917601/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931064] Re: lxc autotest failure with kernel >= 5.13
Marking as invalid as this wasn't an LXC bug but a kernel bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931064 Title: lxc autotest failure with kernel >= 5.13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1931064/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931064] Re: lxc autotest failure with kernel >= 5.13
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=591a22c14d3f45cc38bd1931c593c221df2f1881 ** Changed in: lxc (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931064 Title: lxc autotest failure with kernel >= 5.13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1931064/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1957934] Re: error in man page for lxc.container.conf
** Changed in: lxc (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1957934 Title: error in man page for lxc.container.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1957934/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1126858]
reproduced in: Version: 7.3.0.1 / LibreOffice Community Build ID: 840fe2f57ae5ad80d62bfa6e25550cb10ddabd1d CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1126858 Title: [upstream] Search and replace, with tracked changes on, changing only format of text, causes Writer to hang To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1126858/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1404358]
(In reply to Yurij Z from comment #68) > This bug appears in the new version. > > Shift+Click doesn't work as well as a rectangle-drag selection. > > Version: 7.0.6.2 > Build ID: 00(Build:2) > CPU threads: 8; OS: Linux 5.8; UI render: default; VCL: kf5 > Locale: en-US (en_US.UTF-8); UI: en-US > Ubuntu package version: 1:7.0.6-0ubuntu0.20.10.1 > Calc: threaded > > Writer was running on KDE with "Global scale" ratio of 1.5 (150%) (HiDPI > monitor). Also tested with 100% (no) scaling. Yurij, please try with a current release of LibreOffice (7.1 or 7.2), and if you are still able to reproduce the issue (selecting two rectangles with shift + click), please open a new bug report as this one as already overwhelmingly big. You can then link back to this one in the "see also" field. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1404358 Title: [Upstream] EDITING: multiple graphic objects cannot be selected with key or 'Select' tool with mouse To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1404358/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895157] Re: Boinc cannot enable RPC access to start client or manager
After upgrading to impish (21.10) reverting to the older version from focal (20.04 LTS) still solves the issue for me. boinc_7.16.6+dfsg-1_all.deb (from https://packages.ubuntu.com/focal/boinc) boinc-client_7.16.6+dfsg-1_amd64.deb (from (https://packages.ubuntu.com/focal/boinc-client) boinc-manager_7.16.6+dfsg-1_amd64.deb (from https://packages.ubuntu.com/focal/boinc-manager) libboinc7_7.16.6+dfsg-1_amd64.deb (from https://packages.ubuntu.com/focal/libboinc7) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895157 Title: Boinc cannot enable RPC access to start client or manager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/boinc/+bug/1895157/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951990] [NEW] Package build under hirsute + kernel 5.15.3 FAIL
Public bug reported: Here is output : libtool: link: gcc -fvisibility=hidden -DUNITDIR=\"./unit/\" -DCERTDIR=\"./unit/\" -g -O2 -ffile-prefix-map=/home/bigbob/tmp/Building/iwd/iwd-1.20=. -flto=auto -ffat-lto-objects -fstack-protector-strong -Wformat -Werror=format-security -Wl,-Bsymbolic-functions -flto=auto -Wl,-z -Wl,relro -Wl,-z -Wl,now -o unit/test-eap-mschapv2 src/eap-mschapv2.o src/eap.o src/mschaputil.o unit/test-eap-mschapv2.o ell/.libs/libell-internal.a openssl x509 -req -extensions server_ext \ -extfile ./unit/gencerts.cnf \ -in unit/cert-server.csr -CA ./unit/cert-ca.pem \ -CAkey ./unit/cert-ca-key.pem \ -CAserial ./unit/cert-ca.srl \ -CAcreateserial -sha256 -days 1 -out unit/cert-server.pem Signature ok subject=O = Foo Example Organization, CN = Foo Example Organization, emailAddress = foo@mail.example Getting CA Private Key openssl x509 -req -extensions cert_ext \ -extfile ./unit/gencerts.cnf \ -in unit/cert-client.csr -CA ./unit/cert-ca.pem \ -CAkey ./unit/cert-ca-key.pem \ -CAserial ./unit/cert-ca.srl \ -CAcreateserial -sha256 -days 1 -out unit/cert-client.pem Signature ok subject=O = Bar Example Organization, CN = Bar Example Organization, emailAddress = bar@mail.example Getting CA Private Key PASS: unit/test-hmac-md5 PASS: unit/test-hmac-sha1 PASS: unit/test-hmac-sha256 PASS: unit/test-ie PASS: unit/test-kdf-sha256 PASS: unit/test-mpdu PASS: unit/test-p2p PASS: unit/test-prf-sha1 ./build-aux/test-driver: line 109: 162801 Aborted (core dumped) "$@" > $log_file 2>&1 FAIL: unit/test-sae PASS: unit/test-ssid-security PASS: unit/test-util PASS: unit/test-arc4 PASS: unit/test-band PASS: unit/test-client PASS: unit/test-cmac-aes PASS: unit/test-eap-mschapv2 \ \ \ \ \ \ \ \ \ \ \ \ /bin/bash ./libtool --tag=CC --mode=link gcc -fvisibility=hidden -DUNITDIR=\""./unit/"\" -DCERTDIR=\""./unit/"\" -g -O2 -ffile-prefix-map=/home/bigbob/tmp/Building/iwd/iwd-1.20=. -flto=auto -ffat-lto-objects -fstack-protector-strong -Wformat -Werror=format-security -Wl,-Bsymbolic-functions -flto=auto -Wl,-z,relro -Wl,-z,now -o unit/test-eapol unit/test-eapol.o src/crypto.o src/ie.o src/watchlist.o src/eapol.o src/eapolutil.o src/handshake.o src/eap.o src/eap-tls.o src/eap-ttls.o src/eap-md5.o src/util.o src/eap-tls-common.o src/erp.o src/band.o src/mschaputil.o ell/libell-internal.la PASS: unit/test-crypto libtool: link: gcc -fvisibility=hidden -DUNITDIR=\"./unit/\" -DCERTDIR=\"./unit/\" -g -O2 -ffile-prefix-map=/home/bigbob/tmp/Building/iwd/iwd-1.20=. -flto=auto -ffat-lto-objects -fstack-protector-strong -Wformat -Werror=format-security -Wl,-Bsymbolic-functions -flto=auto -Wl,-z -Wl,relro -Wl,-z -Wl,now -o unit/test-eapol unit/test-eapol.o src/crypto.o src/ie.o src/watchlist.o src/eapol.o src/eapolutil.o src/handshake.o src/eap.o src/eap-tls.o src/eap-ttls.o src/eap-md5.o src/util.o src/eap-tls-common.o src/erp.o src/band.o src/mschaputil.o ell/.libs/libell-internal.a PASS: unit/test-eapol iwd 1.20: ./test-suite.log # TOTAL: 18 # PASS: 17 # SKIP: 0 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 .. contents:: :depth: 2 FAIL: unit/test-sae === test-sae: unit/test-sae.c:129: test_tx_auth_func: Assertion `l_get_le16(frame + 4) == 19' failed. FAIL unit/test-sae (exit status: 134) Testsuite summary for iwd 1.20 # TOTAL: 18 # PASS: 17 # SKIP: 0 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 See ./test-suite.log make[5]: *** [Makefile:2681: test-suite.log] Error 1 make[4]: *** [Makefile:2789: check-TESTS] Error 2 make[3]: *** [Makefile:3133: check-am] Error 2 make[2]: *** [Makefile:3135: check] Error 2 make[2]: Leaving directory '/home/bigbob/tmp/Building/iwd/iwd-1.20' make[1]: *** [debian/rules:15: override_dh_auto_test] Error 2 make[1]: Leaving directory '/home/bigbob/tmp/Building/iwd/iwd-1.20' make: *** [debian/rules:12: binary] Error 2 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 bigbob@bigbob-UX331UN:~/tmp/Building/iwd/iwd-1.20$ Is there a fix somewhere ? ** Affects: iwd (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/1951990 Title: Package build under hirsute + kernel 5.15.3 FAIL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iwd/+bug/1951990/+subscriptions --
[Bug 1950787] Re: systemd-sysusers cannot mount /dev in privileged containers (to pass credentials)
Closing the LXD task as there's not really anything we can do there. The options here are pretty much: - Do nothing, if it's just privileged containers, it's usually not a big deal - Significantly rework apparmor mount handling logic and policies so this can be safely allowed - Ship unit overrides, either though lxd-agent-loader, through a systemd patch or a similar distro mechanism Closing the LXD task as there currently isn't any change we can make to our policies to safely allow this. ** Changed in: lxd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950787 Title: systemd-sysusers cannot mount /dev in privileged containers (to pass credentials) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1950787/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950787] Re: systemd-sysusers cannot mount /dev in privileged containers (to pass credentials)
If this only fails in privileged containers, then I probably wouldn't worry about it too much, those aren't the default and a LOT of things break in privileged containers, so I don't think it's worth doing distro changes to accommodate this, assuming the container otherwise still boots. For cases like this one, it's usually been hard to make a solid case for a change of behavior in upstream systemd. There are a few places like the devices cgroup where permission errors are considered non-fatal which then accommodates containers quite well, but the same isn't true with the isolation security features which this one ties into. In an ideal world, AppArmor would allow us to craft a policy which: - Allows for mount namespaces - Allows for bind-mounts of restricted paths - Applies the parent's policy onto the bind-mount target - Properly support mount propagation flags in a way that can't be abuse to allow all mounts But as it stands, AppArmor is entirely path based, so a policy that applies to /proc will not apply to /proc bind-mount to /blah/proc (which is effectively what systemd does) and so causes all confinement to be bypassable. Additionally, there are (or were in some versions at least) issues with processing those mount propagation flags you see in your log (shared/slave/...) and allowing a bind-mount to be marked using one of those flags would incorrectly cause the parser or the kernel (not quite sure which) to allow ALL mounts... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950787 Title: systemd-sysusers cannot mount /dev in privileged containers (to pass credentials) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1950787/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950787] Re: systemd-sysusers cannot mount /dev in privileged containers (to pass credentials)
Privileged containers have a much stricter apparmor policy applied than unprivileged containers. That's because unprivileged containers primarily rely on the user namespace to prevent breakout and taking over of the host whereas privileged containers rely entirely on apparmor. As apparmor isn't particularly good at dealing with mounts, especially with mount namespaces, there is no safe way for us to allow this operation in privileged containers. As you point out above, we've recently started using a systemd generator to dynamically generate unit overrides based on the environment, letting us disable specific features that interfere with container security. This is used in all of the community images, so in this case you could try it by using "images:ubuntu/jammy" instead of "ubuntu-daily:jammy". We've been considering getting the generator into the lxd-agent-loader package which is included in all Ubuntu images though so far we've found it to be too volatile for that (we were updating it up to twice a week for a while...). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950787 Title: systemd-sysusers cannot mount /dev in privileged containers (to pass credentials) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1950787/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948573] Re: Failure to start container “Failed to start device “eth0”: Error: Unknown device type.
** Package changed: lxd (Ubuntu) => linux-raspi (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1948573 Title: Failure to start container “Failed to start device “eth0”: Error: Unknown device type. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1948573/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947137] Re: package lxd 3.0.3-0ubuntu1~18.04.1 failed to install/upgrade: new lxd package pre-installation script subprocess returned error exit status 1
*** This bug is a duplicate of bug 1712808 *** https://bugs.launchpad.net/bugs/1712808 ** This bug has been marked a duplicate of bug 1712808 udev interface fails in privileged containers -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947137 Title: package lxd 3.0.3-0ubuntu1~18.04.1 failed to install/upgrade: new lxd package pre-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1947137/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908223] Re: nmap 7.80 crashes with Assertion `htn.toclock_running == true'
I have the same problem. With root user only. $ /usr/bin/nmap -sP 192.168.0,10,11,13.* nmap: Target.cc:503: void Target::stopTimeOutClock(const timeval*): Assertion `htn.toclock_running == true' failed. Aborted (core dumped) It only works when setting "-max-parallelism" to a big value. $ /usr/bin/nmap -sP -max-parallelism 1000 192.168.0,10,11,13.* -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908223 Title: nmap 7.80 crashes with Assertion `htn.toclock_running == true' To manage notifications about this bug go to: https://bugs.launchpad.net/nmap/+bug/1908223/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873004] Re: lxd interaction blocked until snapd was restarted
** No longer affects: lxd (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873004 Title: lxd interaction blocked until snapd was restarted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1873004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905478] Re: package lxd 3.0.3-0ubuntu1~18.04.1 failed to install/upgrade: new lxd package pre-installation script subprocess returned error exit status 1
- Setup snap "snapd" (9721) security profiles (cannot reload udev rules: exit status 1 Was that when updating a privileged LXD container by any chance? ** Changed in: lxd (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905478 Title: package lxd 3.0.3-0ubuntu1~18.04.1 failed to install/upgrade: new lxd package pre-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1905478/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908460] Re: package lxd 3.0.3-0ubuntu1~18.04.1 failed to install/upgrade: new lxd package pre-installation script subprocess returned error exit status 143
I suspect you probably found a way out of this by now but if not or if you're hitting this on another system, let me know and I'll sort something out. It would have been interesting to see what those symlinks are pointing to, they may not have been rewritten properly due to the failure partway through the migration. ** Changed in: lxd (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908460 Title: package lxd 3.0.3-0ubuntu1~18.04.1 failed to install/upgrade: new lxd package pre-installation script subprocess returned error exit status 143 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1908460/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909149] Re: package lxd 3.0.3-0ubuntu1~18.04.1 failed to install/upgrade: new lxd package pre-installation script subprocess returned error exit status 1
** Package changed: lxd (Ubuntu) => snapd (Ubuntu) ** Summary changed: - package lxd 3.0.3-0ubuntu1~18.04.1 failed to install/upgrade: new lxd package pre-installation script subprocess returned error exit status 1 + snapd failure when /home is a symlink -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909149 Title: snapd failure when /home is a symlink To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1909149/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909371] Re: package lxd 3.0.3-0ubuntu1~18.04.1 failed to install/upgrade: new lxd package pre-installation script subprocess returned error exit status 1
- Run install hook of "lxd" snap if present (run hook "install": /var/lib/snapd not root-owned 0:110) That's a new one I've never seen before. This suggests that directory ownership for /var/lib/snapd is quite wrong on your system which in turn causes some snapd actions to fail. I'll re-assign to snapd for investigation but it'd be useful if you could show `ls -lh /var/lib/` to see what's going on there. ** Package changed: lxd (Ubuntu) => snapd (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909371 Title: package lxd 3.0.3-0ubuntu1~18.04.1 failed to install/upgrade: new lxd package pre-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1909371/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909693] Re: package lxd (not installed) failed to install/upgrade: new lxd package pre-installation script subprocess returned error exit status 1
- Download snap "snapd" (10492) from channel "stable" (Get https://canonical-bos01.cdn.snapcraft.io/download-origin/canonical- lgw01/PMrrV4ml8uWuEUDBT8dSGnKUYbevVhc4_10492.snap?interactive=1=1609376400_22d9f1ee728894ebbb147d6cf985e1b06e1fbccd: dial tcp 91.189.91.42:443: connect: connection timed out) This shows some kind of network connectivity issue at the time. Re- trying the update, possibly from a different network should unstick things. It may be a good idea for snapd to more actively retry some of those network failures though... ** Changed in: lxd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909693 Title: package lxd (not installed) failed to install/upgrade: new lxd package pre-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1909693/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
