'relative path in ExecStart not valid' vivid local deploy failure

[Martin Packman]

The ci local deploy job on vivid fails on boostrap with:

<http://data.vapour.ws/juju-ci/products/version-2395/local-deploy-vivid-amd64/build-144/consoleText>

Bootstrapping environment "local-deploy-vivid-amd64"
Starting new instance for initial state server
2015-02-28 03:08:04 INFO juju.environs.bootstrap bootstrap.go:180 newest version: 1.23-alpha1.1
2015-02-28 03:08:05 INFO juju.environs.bootstrap bootstrap.go:208 picked bootstrap tools version: 1.23-alpha1.1
Building tools to upload (1.23-alpha1.1-vivid-amd64)
2015-02-28 03:08:05 INFO juju.environs.tools build.go:167 found existing jujud
2015-02-28 03:08:05 INFO juju.environs.tools build.go:177 target: /tmp/juju-tools660181107/jujud
2015-02-28 03:08:18 INFO juju.environs.sync sync.go:323 built tools 1.23-alpha1.1-vivid-amd64 (9601kB)
Installing Juju agent on bootstrap instance
2015-02-28 03:08:18 INFO juju.provider.local environ.go:156 local provider; disabling refreshing OS updates.
2015-02-28 03:08:18 INFO juju.provider.local environ.go:162 local provider; disabling OS upgrades.
Bootstrap failed, destroying environment
2015-02-28 03:08:19 ERROR juju.cmd supercommand.go:430 failed to bootstrap environment: relative path in ExecStart not valid

[Curtis Hovey (sinzui)]

We also see new failures in the vivd unit tests
http://data.vapour.ws/juju-ci/products/version-2400/run-unit-tests-vivid-amd64/build-133/consoleText

VIa Eric Snow:

Looks like my systemd patch broke the vivid tests:

"relative path in ExecStart not valid" [1]

This message from systemd means we are using a relative path somewhere
along the line. I'm guessing that it is the juju datadir. It should
be a simple matter to fix the path (either in juju or in CI).

The problem is likely in the cloudinit script we use during bootstrap.
Is that kept around somewhere? If not, what about the systemd unit
file (in /etc/systemd/)?

[Eric Snow (ericsnowcurrently)]

The patch to add systemd support to juju did not take into account that executable paths may be quoted. The fix is trivial.

[Eric Snow (ericsnowcurrently)]

http://reviews.vapour.ws/r/1047/

[Eric Snow (ericsnowcurrently)]

Also, the issue with failing unit tests appears to be addressed by bug #1427149.

[Eric Snow (ericsnowcurrently)]

The tests are still failing due to lack of support for logfiles in Conf.Output.

[Eric Snow (ericsnowcurrently)]

http://reviews.vapour.ws/r/1051/

[Eric Snow (ericsnowcurrently)]

That appears to have resolve the issue: http://juju-ci.vapour.ws:8080/job/local-deploy-vivid-amd64/157/console

However, that log demonstrates something else is afoot.

[Eric Snow (ericsnowcurrently)]

http://reviews.vapour.ws/r/1053/

[Martin Packman (gz)]

Still failing with the latest change, current error is:

2015-03-03 03:11:04 ERROR juju.cmd supercommand.go:430 No such method 'LinkUnitFiles'

<http://reports.vapour.ws/releases/2404>