Deployer can't deploy local charm with relative path

[Seman]

Deployer is having an issue deploying a bundle that contains a charm with retaliative file path (file path starts with dot)

log:
http://paste.ubuntu.com/16320384/

Bundle (can't find file path ./swift-proxy):
http://paste.ubuntu.com/16319011/

[David Britton (dpb)]

Hi Seman -- Please write the command that failed. Your log obscures that with the 'run_deployer' wrapper.

[Tim Van Steenburgh (tvansteenburgh)]

I don't see any evidence in the log that the relative file path was a problem. The reason for the exit was an invalid config option:

2016-05-06 21:12:00 [ERROR] deployer.deploy: Invalid config charm nova-cloud-controller quantum-security-groups=yes

[Seman (sseman)]

Sorry, I attached the wrong log. Now it has been updated
http://paste.ubuntu.com/16320384/

The Deployer command that failed:
juju --debug deployer -e local.maas-1_9-OS-deployer-juju-2x:maas-1_9-OS-deployer-juju-2x --debug --deploy-delay 10 --timeout 3600 --config /var/lib/jenkins/repository/openstack-baremetal7-next-TESTING.yaml trusty-liberty

2016-05-07 01:52:25 ERROR Command '('juju', '--debug', 'deployer', '-e', 'local.maas-1_9-OS-deployer-juju-2x:maas-1_9-OS-deployer-juju-2x', '--debug', '--deploy-delay', '10', '--timeout', '3600', '--config', '/var/lib/jenkins/repository/openstack-baremetal7-next-TESTING.yaml', 'trusty-liberty')' returned non-zero exit status 1

[Tim Van Steenburgh (tvansteenburgh)]

Seman, do you know if this worked with a prior version of deployer, and if so, which version?

[Tim Van Steenburgh (tvansteenburgh)]

Seman, also can you repaste the contents of the bundle that was used? The link in the description no longer goes to a bundle.

[Seman (sseman)]

Bundle:
http://paste.ubuntu.com/16319011/

Tim, I don't think this worked with prior version. This is first time testing it with a relative path for Juju 2x. In Juju 1x, we just used "local:path" which worked.

The Deployer works if the bundle has an absolute path to the local charm.

[[e-mail] (chocobo777)]

According to
https://jujucharms.com/docs/devel/charms-deploying#deploying-from-a-local-charm
It seems juju 2.0 do not support using a relative path,it needs to be local:~/path

[Andreas Hasenack (ahasenack)]

Confirmed with latest deployer and juju-2:
juju-2.0 2.0-beta16-0ubuntu1~16.04.1~juju1
juju-deployer 0.9.0~bzr190~56~ubuntu16.04.1

2016-09-01 16:37:28 [ERROR] deployer.env: Command (juju deploy -m lxd-controller:admin@local/default --config /tmp/tmpQwV8Ly --series xenial xenial/haproxy-charm haproxy) Output:

 ERROR The charm or bundle "xenial/haproxy-charm" is ambiguous.
To deploy a local charm or bundle, run `juju deploy ./xenial/haproxy-charm`.

Adding an absolute path to the deployer file is awkward and makes it not portable anymore, i.e., I can't just publish it or send it to someone.

[Tim Van Steenburgh (tvansteenburgh)]

Latest build in ppa:tvansteenburgh/ppa