touch-packages team mailing list archive

[Martin Pitt <martin.pitt@xxxxxxxxxx>]

I installed 211 with

  sudo ubuntu-device-flash --verbose --revision=211 core
--output=/tmp/snappy211.img  --developer-mode --channel=ubuntu-core
/devel-proposed

booted it, then run "snappy update". There doesn't seem to be a
parameter to specify the version, so I can't upgrade to 219; it starts
to upgrade straight to 251:

$ sudo snappy versions
Part         Tag   Installed  Available  Fingerprint     Active  
ubuntu-core  edge  211        251        441933324acfd9  *       

However, "snappy update" has spun at "applying [/]" for over half an
hour now. Once it finally succeeds, I'll test the behaviour on the
upgraded image again.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1411112

Title:
  systemd-journal: Failed to join audit multicast group: Operation not
  permitted

Status in systemd package in Ubuntu:
  New

Bug description:
  After upgrading a snappy system from 211 to 219, I'm seeing the
  following errors at boot:

  [   88.772405] systemd-journald[704]: Failed to join audit multicast group: Operation not permitted
  [   88.777304] systemd[1]: Started User Manager for UID 1000.
  [   88.778311] systemd[1]: systemd-journald.service: main process exited, code=exited, status=1/FAILURE
  [   88.778667] systemd[1]: Failed to start Journal Service.

  I've confirmed that a rollback to 211 fixes the problem.

  This makes it impossible to debug changes to snappy itself, since
  snappy logs to syslog which is only available via journalctl.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1411112/+subscriptions