group.of.nepali.translators team mailing list archive

Thread
Date
[Bug 1704677] Re: 229-4ubuntu18: '+' command prefix does not work in ExecStart= and ExecStop=

To: group.of.nepali.translators@xxxxxxxxxxxxxxxxxxx
From: Dimitri John Ledkov <launchpad@xxxxxxxxxxxx>
Date: Mon, 17 Jul 2017 16:05:23 -0000
Reply-to: Bug 1704677 <1704677@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx
systemd (229-4ubuntu19) xenial; urgency=medium

  * debian/extra/units/systemd-resolved.service.d/resolvconf.conf: partially
    revert, by removing ExecStart|StopPost lines, as these are not needed on
    xenial and generate warnings in the journal. (LP: #1704677)

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

  * debian/extra/units/systemd-resolved.service.d/resolvconf.conf: if resolved
    is going to be started, make sure this blocks network-online.target.
    (LP: #1673860)
  * networkd: cherry-pick support for setting bridge port's priority
    (LP: #1668347)
  * Cherrypick upstream commit to enable system use kernel maximum limit for
    RLIMIT_NOFILE isntead of hard-coded (low) limit of 65536. (LP: #1686361)
  * Cherrypick upstream patch for platform predictable interface names.
    (LP: #1686784)
  * resolved: fix null pointer dereference crash (LP: #1621396)
  * Cherrypick core/timer downgrade message about random time addition
    (LP: #1692136)
  * SECURITY UPDATE: Out-of-bounds write in systemd-resolved (LP: #1695546)
    - CVE-2017-9445
  * Cherry-pick subset of patches to introduce infinity value in logind.conf
    for UserTasksMax (LP: #1651518)

Date: Mon, 17 Jul 2017 17:00:42 +0100
Changed-By: Dimitri John Ledkov <xnox@xxxxxxxxxx>
Maintainer: Ubuntu Developers <ubuntu-devel-discuss@xxxxxxxxxxxxxxxx>
https://launchpad.net/ubuntu/+source/systemd/229-4ubuntu19

==

 OK: systemd_229.orig.tar.gz
 OK: systemd_229-4ubuntu19.debian.tar.xz
 OK: systemd_229-4ubuntu19.dsc
     -> Component: main Section: admin

Upload Warnings:
Redirecting ubuntu xenial to ubuntu xenial-proposed.
This upload awaits approval by a distro manager


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

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

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

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

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

** Changed in: systemd (Ubuntu Xenial)
    Milestone: None => ubuntu-16.04.3

** Description changed:

- The systemd version 229-4ubuntu18 from xenial-proposed archive has a
- bug. The '+' prefix (see
- https://www.freedesktop.org/software/systemd/man/systemd.service.html)
- in ExecStart*= and ExecStop*= statements does not work any longer.
+ [Impact]
+ 229-4ubuntu18 included changes irrelevant for xenial, which whilst harmless generates a lot of scary journal entries.
+ 
+ [Fix]
+ Drop the cherrypciked ExecStart|StopPost stanzas from the drop in snippet. Integration of the resolved stub resolver with resolvconf on xenial is not required, because resolved in xenial does not have stub resolver. Also xenial's systemd does not support '+' prefix on the Exec* lines.
+ 
+ [Testcase]
+ Upgrade to te new SRU, make sure testcase from https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1673860 still passes
+ 
+ Check that there is no extra journal warnings/errors about "Executable
+ path is not absolute" from systemd reading /lib/systemd/system/systemd-
+ resolved.service.d/resolvconf.con
+ 
+ [Original Descrption]
+ 
+ 
+ The systemd version 229-4ubuntu18 from xenial-proposed archive has a bug. The '+' prefix (see https://www.freedesktop.org/software/systemd/man/systemd.service.html) in ExecStart*= and ExecStop*= statements does not work any longer.
  
  File /lib/systemd/system/systemd-resolved.service.d/resolvconf.conf of
  this version contains two commands prefixed with '+':
  
  # When resolved is in use, it must be brought up before we consider networking
  # available because otherwise there is a window where DNS resolution doesn't
  # work.
  [Unit]
  Before=network-online.target
  
  # tell resolvconf about resolved's builtin DNS server, so that DNS servers
  # picked up via networkd are respected when using resolvconf, and that software
  # like Chrome that does not do NSS (libnss-resolve) still gets proper DNS
  # resolution
  [Service]
  ExecStartPost=+/bin/sh -c '[ ! -e /run/resolvconf/enable-updates ] || echo "nameserver 127.0.0.53" | /sbin/resolvconf -a systemd-resolved'
  ExecStopPost=+/bin/sh -c '[ ! -e /run/resolvconf/enable-updates ] || /sbin/resolvconf -d systemd-resolved'
  
  Those two statements in section [Service] lead to the following two
  error messages in dmesg:
  
  [    3.687475] systemd[1]: [/lib/systemd/system/systemd-resolved.service.d/resolvconf.conf:12] Executable path is not absolute, ignoring: +/bin/sh -c '[ ! -e /run/resolvconf/enable-updates ] || echo "nameserver 127.0.0.53" | /sbin/resolvconf -a systemd-resolved'
  [    3.687614] systemd[1]: [/lib/systemd/system/systemd-resolved.service.d/resolvconf.conf:13] Executable path is not absolute, ignoring: +/bin/sh -c '[ ! -e /run/resolvconf/enable-updates ] || /sbin/resolvconf -d systemd-resolved'
- --- 
+ ---
  ApportVersion: 2.20.1-0ubuntu2.9
  Architecture: amd64
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 16.04
  MachineType: LENOVO 42406AG
  Package: systemd 229-4ubuntu18
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-85-lowlatency root=UUID=1756e76f-2b6c-479f-8ea3-e3b087b1922f ro quiet apparmor=0
  ProcVersionSignature: Ubuntu 4.4.0-85.108-lowlatency 4.4.73
  Tags: xenial package-from-proposed third-party-packages
  Uname: Linux 4.4.0-85-lowlatency x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom colord davfs2 dialout dip fax floppy libvirtd lpadmin netdev plugdev saned scanner sudo tape video wireshark
  _MarkForUpload: True
  dmi.bios.date: 09/20/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8AET66WW (1.46 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 42406AG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: dmi:bvnLENOVO:bvr8AET66WW(1.46):bd09/20/2016:svnLENOVO:pn42406AG:pvrThinkPadT520:rvnLENOVO:rn42406AG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 42406AG
  dmi.product.version: ThinkPad T520
  dmi.sys.vendor: LENOVO
  mtime.conffile..etc.pam.d.systemd-user: 2017-03-09T13:47:30.332992

** Changed in: systemd (Ubuntu Xenial)
       Status: Triaged => In Progress

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-9445

-- 
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/1704677

Title:
  229-4ubuntu18: '+' command prefix does not work in ExecStart*= and
  ExecStop*=

Status in systemd package in Ubuntu:
  Invalid
Status in systemd source package in Xenial:
  In Progress

Bug description:
  [Impact]
  229-4ubuntu18 included changes irrelevant for xenial, which whilst harmless generates a lot of scary journal entries.

  [Fix]
  Drop the cherrypciked ExecStart|StopPost stanzas from the drop in snippet. Integration of the resolved stub resolver with resolvconf on xenial is not required, because resolved in xenial does not have stub resolver. Also xenial's systemd does not support '+' prefix on the Exec* lines.

  [Testcase]
  Upgrade to te new SRU, make sure testcase from https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1673860 still passes

  Check that there is no extra journal warnings/errors about "Executable
  path is not absolute" from systemd reading /lib/systemd/system
  /systemd-resolved.service.d/resolvconf.con

  [Original Descrption]

  
  The systemd version 229-4ubuntu18 from xenial-proposed archive has a bug. The '+' prefix (see https://www.freedesktop.org/software/systemd/man/systemd.service.html) in ExecStart*= and ExecStop*= statements does not work any longer.

  File /lib/systemd/system/systemd-resolved.service.d/resolvconf.conf of
  this version contains two commands prefixed with '+':

  # When resolved is in use, it must be brought up before we consider networking
  # available because otherwise there is a window where DNS resolution doesn't
  # work.
  [Unit]
  Before=network-online.target

  # tell resolvconf about resolved's builtin DNS server, so that DNS servers
  # picked up via networkd are respected when using resolvconf, and that software
  # like Chrome that does not do NSS (libnss-resolve) still gets proper DNS
  # resolution
  [Service]
  ExecStartPost=+/bin/sh -c '[ ! -e /run/resolvconf/enable-updates ] || echo "nameserver 127.0.0.53" | /sbin/resolvconf -a systemd-resolved'
  ExecStopPost=+/bin/sh -c '[ ! -e /run/resolvconf/enable-updates ] || /sbin/resolvconf -d systemd-resolved'

  Those two statements in section [Service] lead to the following two
  error messages in dmesg:

  [    3.687475] systemd[1]: [/lib/systemd/system/systemd-resolved.service.d/resolvconf.conf:12] Executable path is not absolute, ignoring: +/bin/sh -c '[ ! -e /run/resolvconf/enable-updates ] || echo "nameserver 127.0.0.53" | /sbin/resolvconf -a systemd-resolved'
  [    3.687614] systemd[1]: [/lib/systemd/system/systemd-resolved.service.d/resolvconf.conf:13] Executable path is not absolute, ignoring: +/bin/sh -c '[ ! -e /run/resolvconf/enable-updates ] || /sbin/resolvconf -d systemd-resolved'
  ---
  ApportVersion: 2.20.1-0ubuntu2.9
  Architecture: amd64
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 16.04
  MachineType: LENOVO 42406AG
  Package: systemd 229-4ubuntu18
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-85-lowlatency root=UUID=1756e76f-2b6c-479f-8ea3-e3b087b1922f ro quiet apparmor=0
  ProcVersionSignature: Ubuntu 4.4.0-85.108-lowlatency 4.4.73
  Tags: xenial package-from-proposed third-party-packages
  Uname: Linux 4.4.0-85-lowlatency x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom colord davfs2 dialout dip fax floppy libvirtd lpadmin netdev plugdev saned scanner sudo tape video wireshark
  _MarkForUpload: True
  dmi.bios.date: 09/20/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8AET66WW (1.46 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 42406AG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: dmi:bvnLENOVO:bvr8AET66WW(1.46):bd09/20/2016:svnLENOVO:pn42406AG:pvrThinkPadT520:rvnLENOVO:rn42406AG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 42406AG
  dmi.product.version: ThinkPad T520
  dmi.sys.vendor: LENOVO
  mtime.conffile..etc.pam.d.systemd-user: 2017-03-09T13:47:30.332992

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1704677/+subscriptions
group.of.nepali.translators team mailing list archive

[Bug 1704677] Re: 229-4ubuntu18: '+' command prefix does not work in ExecStart*= and ExecStop*=

[Bug 1704677] Re: 229-4ubuntu18: '+' command prefix does not work in ExecStart= and ExecStop=
