Verification of Plucky, Noble and Jammy =======================================
This is an Ubuntu Core only issue. This was verified here: https://bugs.launchpad.net/snapd/+bug/2106121/comments/3 Tagging to indicate no further testing required: "verification-done-questing verification-done-jammy verification-done- noble verification-done-plucky" ** Description changed: [SRU] 2.71: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/2118396 [ Impact ] + + Ubuntu Core & Snapd snap only OOM for the trigger watch process of systems with limited memory (~ 1 GB) [ Test Plan ] 1. Reproduce with kernel with initrd with snap-bootstrap from snapd deb < 2.70 sudo snap install image-garden image-garden make ubuntu-core-24.x86_64.run QEMU_MEM_OPTION="-m 1024" ./ubuntu-core-24.x86_64.run Wait for the system to boot and observe the last few lines. If need, log in with "ubuntu"/"ubuntu" to inspect the system. 2. Prove fix with kernel with initrd with snap-bootstrap from snapd deb 2.71 Repeat steps for 1 but with image that runs snapd 2.71 Ensure there are no error like "Out of memory: Killed process 172 (snap-bootstrap)" ---original--- The snap-bootstrap "trigger" watch process must have a memory leak, as it's reliably killed by OOM on virtual machines with 1GB of ram. When killed it is showing as actively using (rss) 80-90% of total system memory. To reproduce: sudo snap install image-garden image-garden make ubuntu-core-24.x86_64.run QEMU_MEM_OPTION="-m 1024" ./ubuntu-core-24.x86_64.run Wait for the system to boot and observe the last few lines. If need, log in with "ubuntu"/"ubuntu" to inspect the system. Note that this does NOT prevent the system from booting. Last few lines from my test: [ 4.763074] systemd[1]: plymouth-switch-root.service: Deactivated successfully. [ 4.764173] systemd[1]: Stopped plymouth-switch-root.service - Plymouth switch root service. [ 4.766884] systemd[1]: recovery-chooser-trigger-switchroot.service: Deactivated successfully. [ 4.771278] systemd[1]: Stopped recovery-chooser-trigger-switchroot.service. [ 4.778316] systemd[1]: Starting remount-core-fs.service - Reset propagation of initial mount points... [ 4.781200] systemd[1]: Starting systemd-journald.service - Journal Service... [ 4.784219] systemd[1]: Starting systemd-remount-fs.service - Remount Root and Kernel File Systems... [ 4.792293] systemd[1]: Starting systemd-udev-trigger.service - Coldplug All udev Devices... [ 4.796181] systemd[1]: Finished kmod-static-nodes.service - Create List of Static Device Nodes. [ 4.800997] systemd[1]: [email protected]: Deactivated successfully. [ 4.805917] systemd[1]: Finished [email protected] - Load Kernel Module configfs. [ 4.807669] systemd[1]: modprobe@dm_mod.service: Deactivated successfully. [ 4.808742] systemd-journald[597]: Collecting audit messages is disabled. [ 4.809594] systemd[1]: Finished modprobe@dm_mod.service - Load Kernel Module dm_mod. [ 4.811672] systemd[1]: [email protected]: Deactivated successfully. [ 4.812385] systemd[1]: Finished [email protected] - Load Kernel Module drm. [ 4.813391] systemd[1]: modprobe@efi_pstore.service: Deactivated successfully. [ 4.814085] systemd[1]: Finished modprobe@efi_pstore.service - Load Kernel Module efi_pstore. [ 4.818464] systemd[1]: Started systemd-journald.service - Journal Service. [ 4.975477] loop3: detected capacity change from 0 to 79520 [ 4.994591] systemd-journald[597]: Received client request to flush runtime journal. [ 5.800444] Out of memory: Killed process 172 (snap-bootstrap) total-vm:2948344kB, anon-rss:800128kB, file-rss:0kB, shmem-rss:8960kB, UID:0 pgtables:1868kB oom_score_adj:0 [ 7.610353] /dev/sr0: Can't open blockdev Ubuntu Core 24 on 10.0.2.15 (ttyS0) ubuntu-core-24 login: ** Description changed: [SRU] 2.71: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/2118396 [ Impact ] - Ubuntu Core & Snapd snap only + Ubuntu Core only OOM for the trigger watch process of systems with limited memory (~ 1 GB) [ Test Plan ] 1. Reproduce with kernel with initrd with snap-bootstrap from snapd deb < 2.70 sudo snap install image-garden image-garden make ubuntu-core-24.x86_64.run QEMU_MEM_OPTION="-m 1024" ./ubuntu-core-24.x86_64.run Wait for the system to boot and observe the last few lines. If need, log in with "ubuntu"/"ubuntu" to inspect the system. 2. Prove fix with kernel with initrd with snap-bootstrap from snapd deb 2.71 Repeat steps for 1 but with image that runs snapd 2.71 Ensure there are no error like "Out of memory: Killed process 172 (snap-bootstrap)" ---original--- The snap-bootstrap "trigger" watch process must have a memory leak, as it's reliably killed by OOM on virtual machines with 1GB of ram. When killed it is showing as actively using (rss) 80-90% of total system memory. To reproduce: sudo snap install image-garden image-garden make ubuntu-core-24.x86_64.run QEMU_MEM_OPTION="-m 1024" ./ubuntu-core-24.x86_64.run Wait for the system to boot and observe the last few lines. If need, log in with "ubuntu"/"ubuntu" to inspect the system. Note that this does NOT prevent the system from booting. Last few lines from my test: [ 4.763074] systemd[1]: plymouth-switch-root.service: Deactivated successfully. [ 4.764173] systemd[1]: Stopped plymouth-switch-root.service - Plymouth switch root service. [ 4.766884] systemd[1]: recovery-chooser-trigger-switchroot.service: Deactivated successfully. [ 4.771278] systemd[1]: Stopped recovery-chooser-trigger-switchroot.service. [ 4.778316] systemd[1]: Starting remount-core-fs.service - Reset propagation of initial mount points... [ 4.781200] systemd[1]: Starting systemd-journald.service - Journal Service... [ 4.784219] systemd[1]: Starting systemd-remount-fs.service - Remount Root and Kernel File Systems... [ 4.792293] systemd[1]: Starting systemd-udev-trigger.service - Coldplug All udev Devices... [ 4.796181] systemd[1]: Finished kmod-static-nodes.service - Create List of Static Device Nodes. [ 4.800997] systemd[1]: [email protected]: Deactivated successfully. [ 4.805917] systemd[1]: Finished [email protected] - Load Kernel Module configfs. [ 4.807669] systemd[1]: modprobe@dm_mod.service: Deactivated successfully. [ 4.808742] systemd-journald[597]: Collecting audit messages is disabled. [ 4.809594] systemd[1]: Finished modprobe@dm_mod.service - Load Kernel Module dm_mod. [ 4.811672] systemd[1]: [email protected]: Deactivated successfully. [ 4.812385] systemd[1]: Finished [email protected] - Load Kernel Module drm. [ 4.813391] systemd[1]: modprobe@efi_pstore.service: Deactivated successfully. [ 4.814085] systemd[1]: Finished modprobe@efi_pstore.service - Load Kernel Module efi_pstore. [ 4.818464] systemd[1]: Started systemd-journald.service - Journal Service. [ 4.975477] loop3: detected capacity change from 0 to 79520 [ 4.994591] systemd-journald[597]: Received client request to flush runtime journal. [ 5.800444] Out of memory: Killed process 172 (snap-bootstrap) total-vm:2948344kB, anon-rss:800128kB, file-rss:0kB, shmem-rss:8960kB, UID:0 pgtables:1868kB oom_score_adj:0 [ 7.610353] /dev/sr0: Can't open blockdev Ubuntu Core 24 on 10.0.2.15 (ttyS0) ubuntu-core-24 login: ** Tags removed: verification-needed verification-needed-jammy verification-needed-noble verification-needed-plucky ** Tags added: verification-done-jammy verification-done-noble verification-done-plucky ** Tags added: verification-done-questing -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2106121 Title: snap-bootstrap OOM in the trigger watch process To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/2106121/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
