[Touch-packages] [Bug 1480310] Re: systemctl link request failed for service FOO: Unit name FOO is not valid.
Also confirmed via the Ubuntu charm amulet test in uosci, that Wily is deployable again. Thanks, all! http://paste.ubuntu.com/12238490/ -- 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: Fix Released 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 -- 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
[Touch-packages] [Bug 1480310] Re: systemctl link request failed for service FOO: Unit name FOO is not valid.
Juju CI confirms this is fixed: http://reports.vapour.ws/releases/3016/job/local-deploy-wily-amd64/attempt/297 ** Changed in: juju-core Status: Triaged = 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: Fix Released 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 -- 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
[Touch-packages] [Bug 1480310] Re: systemctl link request failed for service FOO: Unit name FOO is not valid.
** Changed in: juju-core Milestone: 1.25-alpha1 = 1.25-beta1 -- 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 Committed 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
[Touch-packages] [Bug 1480310] Re: systemctl link request failed for service FOO: Unit name FOO is not valid.
This bug was fixed in the package systemd - 224-2ubuntu2 --- systemd (224-2ubuntu2) wily; urgency=medium * Cherry-pick FTBFS (with pkg-create-dbgsym) fix from Debian master branch. systemd (224-2ubuntu1) wily; urgency=medium * Merge with Debian unstable. Remaining Ubuntu changes: - Hack to support system-image read-only /etc, and modify files in /etc/writable/ instead. - Keep our much simpler udev maintainer scripts (all platforms must support udev, no debconf). - initramfs init-bottom: If LVM is installed, settle udev, otherwise we get missing LV symlinks. Workaround for LP #1185394. - Add debian/udev.lvm2.init: Dummy SysV init script to satisfy insserv dependencies to lvm2 which is handled with udev rules in Ubuntu. - Add debian/udev.lvm2.service to avoid running the dummy lvm2 init script. - Provide shutdown fallback for upstart. (LP: #1370329) - debian/extra/ifup@.service: Additionally run for auto class. We don't really support allow-hotplug in Ubuntu at the moment, so we need to deal with auto devices appearing after /etc/init.d/networking start already ran. (LP: #1374521) - ifup@.service: Drop dependency on networking.service (i. e. /etc/init.d/networking), and merely ensure that /run/network exists. This avoids unnecessary dependencies/waiting during boot and dependency cycles if hooks wait for other interfaces to come up (like ifenslave with bonding interfaces). (LP: #1414544) - Add Get-RTC-is-in-local-time-setting-from-etc-default-rc.patch: In Ubuntu we currently keep the setting whether the RTC is in local or UTC time in /etc/default/rcS UTC=yes|no, instead of /etc/adjtime. (LP: #1377258) - Put session scopes into all cgroup controllers. This makes unprivileged user LXC containers work under systemd. (LP: #1346734) - systemctl: Don't forward telinit u to upstart. This works around upstart's Restart() always reexec'ing /sbin/init on Restart(), even if that changes to point to systemd during the upgrade. This avoids running systemd during a dist-upgrade. (LP: #1430479) - Drop hwdb-update dependency from udev-trigger.service, which got introduced in v219-stable. This causes udev and plymouth to start too late and isn't really needed in Ubuntu yet as we don't support stateless systems yet and handle hwdb.bin updates through dpkg triggers. This can be dropped again with initramfs-tools 0.117. - Lower Breaks: to plymouth version which has the udev inotify fix in Ubuntu. - Lower apparmor Breaks: to the Ubuntu version that dropped $remote_fs. - Change systemd-sysv's conflicts to upstart-sysv. (LP: #1422681) Upgrade fixes, keep until 16.04 LTS release: - systemd Conflicts/Replaces/Provides systemd-services. - Remove obsolete systemd-logind upstart job. - Clean up obsolete /etc/udev/rules.d/README. - systemd.postinst: Migrate mountall specific fstab options to standard util-linux nofail option. * Don't build new systemd-journal-remote package and drop libmicrohttpd-dev. This is blocked by the MIR (LP #1488341) and feature freeze. systemd (224-3) UNRELEASED; urgency=medium * Add better fix for systemctl link/enable breakage with full paths. (LP: #1480310) * debian/rules: Add missing $(dh_options) in overridden debhelper targets. systemd (224-2) unstable; urgency=medium [ Martin Pitt ] * 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) * debian/extra/rules-ubuntu/40-hyperv-hotadd.rules: Also apply to Xen, and rename to 40-vm-hotadd.rules. * Fix networkd crash. (Closes: #796358) * debian/rules: Remove all files/empty dirs in systemd which are already shipped by systemd-* or udev, instead of an explicit list. * Bump mount dependency to = 2.26, to ensure swapon -o availability. (Closes: #796389) * Install /lib/systemd/network/* into udev instead of systemd, as it's really udev which is evaluating these. * Split out systemd-container package with machined and nspawn and enable importd. Add new libbz2-dev, zlib1g-dev, and libcurl-dev build deps. (LP: #1448900) * Move transitional libgcrypt11-dev build dep to libgcrypt20-dev. * debian/rules: Limit check for libraries in /usr to systemd and udev packages, as other packages like systemd-containers can (and do) link to /usr. * Build-depend on dpkg-dev (= 1.17.14) and bump debhelper version for build profiles support. * Drop display-managers autopkgtest, obsolete with dropped default-display-manager-generator. * boot-and-services autopkgtest: Add systemd-container
[Touch-packages] [Bug 1480310] Re: systemctl link request failed for service FOO: Unit name FOO is not valid.
** 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: In Progress 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
[Touch-packages] [Bug 1480310] Re: systemctl link request failed for service FOO: Unit name FOO is not valid.
Ah, this indeed does not only affect the link command but others too. I'm just confused -- why do you call link *and* enable with an absolute path? You can just do the latter, that implies link. Or you explicitly link and then usually call enable on a name only, not a path. Either way, https://github.com/systemd/systemd/pull/1044 should fix this in a more generic fashion, I'm testing this now. ** Changed in: systemd (Ubuntu) Status: Fix Released = In Progress -- 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: In Progress 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
[Touch-packages] [Bug 1480310] Re: systemctl link request failed for service FOO: Unit name FOO is not valid.
** Changed in: systemd (Ubuntu) Status: In Progress = Fix Committed -- 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 Committed 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
[Touch-packages] [Bug 1480310] Re: systemctl link request failed for service FOO: Unit name FOO is not valid.
On Jul 28, uosci was able to deploy Wily @ Juju 1.24.2. Granted, that was with older Wily images and perhaps older systemd, so it may or may not be helpful information at this point. Here is that successful amulet test output from the trusty/ubuntu charm, which exercises all currently-supported Ubuntu releases (+ current dev Ubuntu release): charm_amulet_test/5429: http://paste.ubuntu.com/12193551/ I think it may be of interest to begin cycling the trusty/ubuntu charm's amulet test in Juju CI as an easy way to do a really basic and quick functional check. ie. grab lp:charms/trusty/ubuntu, then make functional_test. The tests are maintained and validated as Ubuntu releases come and go. Note that tests are only added and enabled for Ubuntu dev versions after confirming that they pass for that version. http://bazaar.launchpad.net/~charmers/charms/trusty/ubuntu/trunk/files/head:/tests/ The Ubuntu charm is, and is intended to be, a minimal hookless nothing. That makes it attractive for inexpensive general validation of test automation, environments, tooling and such (which is uosci's specific interest in it). That could also make it attractive for testing Ubuntu releases vs. Juju releases. -- 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 -- 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
[Touch-packages] [Bug 1480310] Re: systemctl link request failed for service FOO: Unit name FOO is not valid.
FYI duplicate was @ https://bugs.launchpad.net/juju-core/+bug/1488554. Thanks for pointing it here. -- 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 -- 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
[Touch-packages] [Bug 1480310] Re: systemctl link request failed for service FOO: Unit name FOO is not valid.
The duplicate bug confirms what we are seeing in CI wily + 1.24.5: Failed to execute operation: Unit name /etc/systemd/system/juju-clean-shutdown.service is not valid -- 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 -- 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
[Touch-packages] [Bug 1480310] Re: systemctl link request failed for service FOO: Unit name FOO is not valid.
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 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 -- 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
[Touch-packages] [Bug 1480310] Re: systemctl link request failed for service FOO: Unit name FOO is not valid.
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.p...@ubuntu.com 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 -- 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
[Touch-packages] [Bug 1480310] Re: systemctl link request failed for service FOO: Unit name FOO is not valid.
Quick workaround: Use systemctl --global link foo.service to forego the SELinux check. -- 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: In Progress 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
[Touch-packages] [Bug 1480310] Re: systemctl link request failed for service FOO: Unit name FOO is not valid.
Fixed in packaging git. ** Changed in: systemd (Ubuntu) Status: In Progress = Fix Committed -- 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 Committed 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
[Touch-packages] [Bug 1480310] Re: systemctl link request failed for service FOO: Unit name FOO is not valid.
** Changed in: systemd (Ubuntu) Importance: Undecided = High -- 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: In Progress 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
[Touch-packages] [Bug 1480310] Re: systemctl link request failed for service FOO: Unit name FOO is not valid.
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
[Touch-packages] [Bug 1480310] Re: systemctl link request failed for service FOO: Unit name FOO is not valid.
I created an autopkgtest: http://paste.ubuntu.com/12009633/ Bisecting now. ** Changed in: systemd (Ubuntu) Status: Triaged = In Progress ** Changed in: systemd (Ubuntu) Assignee: Martin Pitt (pitti) = (unassigned) -- 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: In Progress 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
[Touch-packages] [Bug 1480310] Re: systemctl link request failed for service FOO: Unit name FOO is not valid.
Bisected to https://github.com/systemd/systemd/commit/4938696301a914ec26bcfc60bb99a1e9624e3789 -- 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: In Progress 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
