touch-packages team mailing list archive

[Launchpad Bug Tracker <1480310@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package systemd - 224-1ubuntu3

---------------
systemd (224-1ubuntu3) wily; urgency=medium

  * Skip systemd-fsckd autopkgtest if /run/initramfs/fsck-root exists, i. e.
    the initramfs already ran fsck.
  * Fix broken ACL in tmpfiles.d/systemd.conf. (Closes: #794645, LP: #1480552)
  * Add debian/tests/unit-config: Test "systemctl link"; reproduces LP#1480310.
  * Add a hack to unbreak "systemctl link". (LP: #1480310)

 -- Martin Pitt <martin.pitt@xxxxxxxxxx>  Wed, 12 Aug 2015 15:21:19
+0200

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

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

Title:
  systemctl link request failed for service FOO: Unit name FOO is not
  valid.

Status in juju-core:
  Triaged
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  As seen in
      http://reports.vapour.ws/releases/2936/job/local-deploy-wily-amd64/attempt/136
  Juju cannot bootstrap on wily because 
     ERROR juju.service.systemd service.go:149 dbus link request failed for service
      "juju-db-jenkins-local-deploy-wily-amd64": Unit name
      /var/lib/juju/init/juju-db-jenkins-local-deploy-wily-amd64/juju-db-jenkins-local-deploy-wily-amd64.service
      is not valid.

  This error first occurred after the wily-slave got package updates.
  The released jujus get the same errors as the jujus under test. This
  issue is probably an Ubuntu packaging break.

  I am making the test non-voting since we can see table 1.24.3 no
  longer works.

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1480310/+subscriptions