[Bug 1616422] Re: [trusty SRU/FFE] Add systemd binary package for snapd

[Po-Hsu Lin]

Hello Martin,

hello world does not work as well, but core snap can be installed
without any problem.

ubuntu at ubuntu:~$ snap list
Name  Version  Rev  Developer  Notes
core  16.04.1  394  canonical  -
ubuntu at ubuntu:~$ uname -a
Linux ubuntu 3.13.0-102-generic #149-Ubuntu SMP Wed Nov 9 21:52:08 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
ubuntu at ubuntu:~$ dpkg -l | grep systemd
ii  libpam-systemd:amd64                  204-5ubuntu20.20                               amd64        system and service manager - PAM module
ii  libsystemd-daemon0:amd64              204-5ubuntu20.20                               amd64        systemd utility library
ii  libsystemd-journal0:amd64             204-5ubuntu20.20                               amd64        systemd journal utility library
ii  libsystemd-login0:amd64               204-5ubuntu20.20                               amd64        systemd login utility library
ii  systemd                               204-5ubuntu20.20                               amd64        system and service manager
ii  systemd-services                      204-5ubuntu20.20                               amd64        systemd runtime services
rc  systemd-shim                          6-2bzr1                                        amd64        shim for systemd


ubuntu at ubuntu:~$ sudo snap install hello-world
[sudo] password for ubuntu: 
error: cannot perform the following tasks:
- Setup snap "hello-world" (27) security profiles (cannot setup apparmor for snap "hello-world": cannot load apparmor profile "snap.hello-world.env": cannot load apparmor profile: exit status 1
apparmor_parser output:
AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.hello-world.env in /var/lib/snapd/apparmor/profiles/snap.hello-world.env at line 305: syntax error, unexpected TOK_CONDLISTID, expecting TOK_MODE
)
- Setup snap "hello-world" (27) security profiles (cannot load apparmor profile "snap.hello-world.env": cannot load apparmor profile: exit status 1
apparmor_parser output:
AppArmor parser error for /var/lib/snapd/apparmor/profiles/snap.hello-world.env in /var/lib/snapd/apparmor/profiles/snap.hello-world.env at line 305: syntax error, unexpected TOK_CONDLISTID, expecting TOK_MODE
)

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1616422

Title:
  [trusty SRU/FFE] Add systemd binary package for snapd

Status in init-system-helpers package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid
Status in init-system-helpers source package in Trusty:
  Fix Committed
Status in systemd source package in Trusty:
  Fix Committed

Bug description:
  Rationale: For backporting snapd to 14.04 LTS, we need to provide
  systemd's service manager (not just logind and auxiliary services like
  logind or timesyncd). upstart will continue to do the actual booting,
  and systemd will act as a "deputy init" which by default does not ship
  with/start any services by itself. We will only support this on server
  (at the first iteration at least), not on desktops.

  Regression potential: This is a new binary package in universe, so
  existing systems are unaffected (provided that we ensure that the
  other binary packages do not change and there are no code changes that
  affect processes other than the "deputy pid 1" service manager). So
  for plain upgrades the regression potential is very low. However,
  there is a medium potential for breakage when actually installing the
  new systemd package, as it might interfere with upstart jobs or other
  running processes, cause boot/shutdown hangs, etc.

  For init-system-helpers, the regression potential is near-zero: We
  never had (and never will) systemd as pid 1 in trusty, so deb-systemd-
  invoke was previously never called. It does get called now if you
  install Ubuntu packages that ship a systemd unit, so we need to make
  that a no-op to retain the current behaviour.

  Test plan:
   1. Dist-upgrade a trusty installation to the proposed versions. Ensure this does not pull in "systemd", and that booting, shutdown, desktop startup, suspend on lid close, resume, logout, and user switching all still work.

   2. Install the "systemd" binary package (this will replace/remove
  systemd-shim). Verify that you can talk to the service manager with
  "sudo systemctl status". Check that booting and shutdown continues to
  work without (significant) delays.

   3. Ensure that "sudo journalctl" works and that "sudo systemctl
  status systemd-journald" is running and has a few lines of log at the
  end (unlike what you get when you run systemctl as user).

   4. Install a package that ships a systemd .service file, such as
  "haveged". Ensure that the service file is ignored, "pgrep -af
  haveged" should only have *one* process and "systemctl status haveged"
  should not be running (it should not exist, or not be enabled and be
  inactive). [This part also needs the updated init-system-helpers].

     The only services that are running are expected to be systemd-
  journald.service and systemd-journald.socket.

   5. Ensure that the standard targets are active, as that is where
  third-party/snap services hook into:

      systemctl status sysinit.target multi-user.target default.target

   6. Install snapd (not in trusty yet, e. g. from Thomas' PPA) and
  ensure you can install a snap, and its services start after installing
  the snap and after rebooting.

   7. Run "sudo apt-get install --reinstall systemd" to ensure that
  upgrades to newer systemd trusty versions work. The running systemd
  should *not* be restarted as that would disrupt snapd and its services
  (verify that the pid in "initctl status systemd" is the same before
  and after the upgrade).

   8. Run "sudo apt install -y colord && sudo apt purge -y colord". This
  should succeed.

   9. Dist-upgrade to 16.04 to ensure that there are no file conflicts,
  dependency issues, etc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1616422/+subscriptions