** Description changed: [SRU] 2.73: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/2132084 [ Impact ] - <add info...> + Snapd becomes unusable when restarting with large set of prompting rules + because the requestrules backend would record a notice for every rule. [ Test Plan ] 1. Reproduce with snapd snap < 2.73 - <add info...> + - Setup 10002 permission prompting rules + - Reboot + - Confirm 100% CPU load, and snap commands time out 2. Prove fixed with snapd snap 2.73 - <add info...> + - Setup 10002 permission prompting rules + - Reboot + - Confirm no disabling and long lasting spike in CPU load and snapd API access + continues to work. ---original--- I have created 10002 permission prompting rules. Snapd were able to handle them gracefully with the benchmark I was running it against. However, on reboot, snapd hits 100% CPU and never starts, snap commands time out and so on. When removing /var/lib/snapd/interfaces-requests OR when disabling the permission experiment, a restart makes snapd functional. Snap version returns for instance: $ snap version snap 2.71.1+ubuntu25.10.1 snapd unavailable series - and because of this, I couldn’t return a stacktrace with: $ sudo snap debug stacktraces error: cannot communicate with server: timeout exceeded while waiting for response I have thus sent a SIGABTR to snapd and attach the stacktrace from the journal.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2127189 Title: Too many permission prompting rules can prevent snapd to start To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/2127189/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
