Confirmed, and forwarded to
https://github.com/systemd/systemd/issues/879 .
** Summary changed:
- dbus link request failed for service FOO: Unit name FOO is not valid.
+ systemctl link request failed for service FOO: Unit name FOO is not valid.
** Changed in: systemd (Ubuntu)
Status: Confirmed => Triaged
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
--
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:
Triaged
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
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
