wily + 1.24.5: Failed to execute operation: Unit name /etc/systemd/system/juju-clean-shutdown.service is not valid

[Ryan Beisner]

With juju 1.24.5 (and 1.24.3), deploying Wily services fails. This is observed on our private test cloud (serverstack).

Observation from the juju user perspective is that the units stay "Waiting for agent initialization to finish" until the deployment ultimately times out. Meanwhile, we are able to ssh into the instances that would have become juju units. The juju agent is not installed, and errors are present in syslog.

# syslog interesting bits (see attached bz2):
Aug 25 14:02:06 ubuntu cloud-init[3716]: Failed to execute operation: Unit name /etc/systemd/system/juju-clean-shutdown.service is not valid.
Aug 25 14:02:06 ubuntu cloud-init[3716]: Cloud-init v. 0.7.7 running 'modules:final' at Tue, 25 Aug 2015 14:02:06 +0000. Up 37.14 seconds.
Aug 25 14:02:06 ubuntu cloud-init[3716]: 2015-08-25 14:02:06,621 - util.py[WARNING]: Failed running /var/lib/cloud/instance/scripts/runcmd [1]
Aug 25 14:02:06 ubuntu cloud-init[3716]: 2015-08-25 14:02:06,625 - cc_scripts_user.py[WARNING]: Failed to run module scripts-user (scripts in /var/lib/cloud/instance/scripts)
Aug 25 14:02:06 ubuntu cloud-init[3716]: 2015-08-25 14:02:06,626 - util.py[WARNING]: Running module scripts-user (<module 'cloudinit.config.cc_scripts_user' from '/usr/lib/python3/dist-packages/cloudinit/config/cc_scripts_user.py'>) failed

# Simple reproducer:
juju-deployer -B -v -c ubuntu3.yaml -d wily
Using bundle from: http://bazaar.launchpad.net/~ost-maintainers/openstack-charm-testing/trunk/view/head:/bundles/other/ubuntu3.yaml

@ 1.24.3 & 1.24.5 + ubuntu-daily/ubuntu-wily-daily-amd64-server-20150821-disk1.img:
Succeeds with Precise, Trusty, Vivid.
Fails with Wily .

[Ryan Beisner (1chb1n)]

While helping to troubleshoot, rharper also observed:

<rharper> beisner: it appears that juju needs to put that service file in /lib/systemd/system and symlink it into the etc dir they do

<rharper> I don't know why; but if you look at /etc/systemd/system , all other services there are symlinks into /lib/systemd/system files

<rharper> if I move and symlink, then it works fine

<rharper> beisner: http://paste.ubuntu.com/12193071/

[Cheryl Jennings (cherylj)]

This is most likely a dup of bug #1480310

[Ryan Beisner (1chb1n)]

FYI I just updated the bug description. I was in error that this image worked with 1.24.3. I just re-deployed to re-confirm. We do experience the same failure with 1.24.3 as with 1.24.5.