We are still seeing this issue after getting this fix and rebooting the
machine:
jenkins@wily-slave:~$ apt-cache policy systemd
systemd:
Installed: 224-1ubuntu3
Candidate: 224-1ubuntu3
Version table:
*** 224-1ubuntu3 0
500 http://archive.ubuntu.com/ubuntu/ wily/main amd64 Packages
100 /var/lib/dpkg/status
2015-08-14 13:19:28 ERROR juju.service.systemd service.go:452 failed to install
service "juju-db-jenkins-local-deploy-wily-amd64": dbus enable 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.
2015-08-14 13:19:28 ERROR juju.cmd supercommand.go:429 dbus enable 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.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1480310
Title:
systemctl link request failed for service FOO: Unit name FOO is not
valid.
To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1480310/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
