group.of.nepali.translators team mailing list archive

[Dimitri John Ledkov <launchpad@xxxxxxxxxxxx>]

That was not useful at all @ogra @mvo
As on the 18th systemd migrated that can set Nice in artful.... yet you disabled it on the 18th.

Please back out your comment, and re-enable setting Nice in artful.

Manually uncommenting and rebooting artful container results in:

Aug 21 12:35:23 noinit systemd[329]: snapd.service: Failed to adjust OOM setting, assuming containerized execution, ignoring: Permission denied
Aug 21 12:35:23 noinit systemd[329]: snapd.service: Failed to adjust Nice setting, assuming containerized execution, ignoring: Operation not permitted
Aug 21 12:35:23 noinit systemd[329]: snapd.service: Executing: /usr/lib/snapd/snapd


** Also affects: systemd (Ubuntu Artful)
   Importance: High
     Assignee: Dimitri John Ledkov (xnox)
       Status: Fix Committed

** Also affects: systemd (Ubuntu Xenial)
   Importance: Undecided
       Status: New

** Changed in: systemd (Ubuntu Xenial)
       Status: New => Confirmed

** Changed in: systemd (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: systemd (Ubuntu Xenial)
     Assignee: (unassigned) => Dimitri John Ledkov (xnox)

** Changed in: systemd (Ubuntu Artful)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1709536

Title:
  snapd 2.26.14 on ubuntu-core won't start in containers anymore

Status in snapd:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Confirmed
Status in systemd source package in Artful:
  Fix Released

Bug description:
  It looks like snapd in ubuntu-core (2.26.14 here) has been modified to
  use a negative Nice value in systemd. Systemd seems to treat a failure
  to apply the requested Nice value as critical to unit startup.

  Unprivileged LXD containers do not allow the use of negative nice
  values as those are restricted to the real root user. I believe the
  optimal fix would be for systemd to ignore permission errors when
  attempting to setup such custom nice values in containers but if that
  can't be resolved quickly, then it means that snapd will now fail to
  start inside containers.

  
  Aug 09 05:54:37 core systemd[1]: snapd.service: Main process exited, code=exited, status=201/NICE
  Aug 09 05:54:37 core systemd[1]: snapd.service: Unit entered failed state.
  Aug 09 05:54:37 core systemd[1]: snapd.service: Failed with result 'exit-code'.

  
  I have confirmed that setting up a unit override by hand which sets Nice=0 does resolve the problem, confirming that the negative Nice value is the problem (snapd.service has Nice=-5 here).

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1709536/+subscriptions