[Group.of.nepali.translators] [Bug 1709536] Re: snapd 2.26.14 on ubuntu-core won't start in containers anymore

2020-06-01 Thread Stéphane Graber 
** Changed in: layer-snap
   Status: New => Invalid

-- 
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 Snap Layer:
  Invalid
Status in snapd:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Released
Status in systemd source package in Artful:
  Fix Released

Bug description:
  [Impact]

  Systemd treats 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. snapd will fail to start inside containers now that snapd uses
  a negative Nice value.

  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'.

  The fix is for systemd to ignore permission errors when attempting to
  setup such custom nice values in containers.

  I have confirmed that setting up a unit override by hand which sets
  Nice = 0 does resolve the problem.

  [Test Case]

  Boot a Xenial image in lxd:

  $ lxc launch xenial x1
  $ lxc exec x1 -- systemctl --state=failed

  Observe failures for snapd :

  ● snapd.service loaded failed failed Snappy daemon
  ● snapd.socket loaded failed failed Socket activation for snapp

  Install updated systemd from -proposed and get status: (lxc exec
   reboot; lxc exec  systemctl status)

  State: running
  Jobs: 0 queued
  Failed: 0 units

  [Regression Potential]

  Services will now run with a Nice value other than what was specified
  in the unit if it cannot be changed for some reason.

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1709536] Re: snapd 2.26.14 on ubuntu-core won't start in containers anymore

2018-01-02 Thread Michael Vogt 
** Changed in: snapd
   Status: New => 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 Snap Layer:
  New
Status in snapd:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Released
Status in systemd source package in Artful:
  Fix Released

Bug description:
  [Impact]

  Systemd treats 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. snapd will fail to start inside containers now that snapd uses
  a negative Nice value.

  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'.

  The fix is for systemd to ignore permission errors when attempting to
  setup such custom nice values in containers.

  I have confirmed that setting up a unit override by hand which sets
  Nice = 0 does resolve the problem.

  [Test Case]

  Boot a Xenial image in lxd:

  $ lxc launch xenial x1
  $ lxc exec x1 -- systemctl --state=failed

  Observe failures for snapd :

  ● snapd.service loaded failed failed Snappy daemon
  ● snapd.socket loaded failed failed Socket activation for snapp

  Install updated systemd from -proposed and get status: (lxc exec
   reboot; lxc exec  systemctl status)

  State: running
  Jobs: 0 queued
  Failed: 0 units

  [Regression Potential]

  Services will now run with a Nice value other than what was specified
  in the unit if it cannot be changed for some reason.

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1709536] Re: snapd 2.26.14 on ubuntu-core won't start in containers anymore

2017-10-23 Thread Launchpad Bug Tracker 
This bug was fixed in the package systemd - 229-4ubuntu20

---
systemd (229-4ubuntu20) xenial; urgency=medium

  * resolved: recognize DNS names with more than one trailing dot as invalid
(LP: #160)
  * Ignore failures to set Nice priority on services in containers.
(LP: #1709536)
  * networkd: accept `:' in ifnames in systemd/networkd. (LP: #1714933)
  * initramfs-tools: trigger udevadm add actions with subsystems first.
(LP: #1713536)
  * networkd: Add support to set STP value on a bridge. (LP: #1665088)
  * networkd: add support for AgeingTImeSec, Priority and DefaultPVID settings.
(LP: #1715131)
- Drop cherrypick of uint16 config parser, superseeded by above commit.
  * networkd: add support to set ActiveSlave and PrimarySlave. (LP: #1709135)
- networkd: add support to configure ARP, depedency of Primary/ActiveSlave.

 -- Dimitri John Ledkov   Tue, 05 Sep 2017 14:01:51
+0100

** Changed in: systemd (Ubuntu Xenial)
   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 Snap Layer:
  New
Status in snapd:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Released
Status in systemd source package in Artful:
  Fix Released

Bug description:
  [Impact]

  Systemd treats 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. snapd will fail to start inside containers now that snapd uses
  a negative Nice value.

  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'.

  The fix is for systemd to ignore permission errors when attempting to
  setup such custom nice values in containers.

  I have confirmed that setting up a unit override by hand which sets
  Nice = 0 does resolve the problem.

  [Test Case]

  Boot a Xenial image in lxd:

  $ lxc launch xenial x1
  $ lxc exec x1 -- systemctl --state=failed

  Observe failures for snapd :

  ● snapd.service loaded failed failed Snappy daemon
  ● snapd.socket loaded failed failed Socket activation for snapp

  Install updated systemd from -proposed and get status: (lxc exec
   reboot; lxc exec  systemctl status)

  State: running
  Jobs: 0 queued
  Failed: 0 units

  [Regression Potential]

  Services will now run with a Nice value other than what was specified
  in the unit if it cannot be changed for some reason.

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1709536] Re: snapd 2.26.14 on ubuntu-core won't start in containers anymore

2017-08-28 Thread Stuart Bishop 
** Also affects: layer-snap
   Importance: Undecided
   Status: New

** Changed in: layer-snap
   Importance: Undecided => Critical

-- 
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 Snap Layer:
  New
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/layer-snap/+bug/1709536/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1709536] Re: snapd 2.26.14 on ubuntu-core won't start in containers anymore

2017-08-21 Thread Dimitri John Ledkov 
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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp