cf-charmers team mailing list archive

[Alexander Lomov <lomov.as@xxxxxxxxx>]

Still have this issue even after virtual box recreation.

I created new vagrant box with trusty and used archive from ppa:juju/stable
to install juju.
I've got 1.18.0-trusty-amd64 juju version installed (this is output of
`juju version` command) .
Used `sudo apt-get install deployer` to install juju deployer.
After that I had following output:

https://gist.github.com/allomov/10366236

python version is 2.7.6




On 10 April 2014 02:12, Alexander Lomov <lomov.as@xxxxxxxxx> wrote:

> Hey, all.
>
> It seems that I broke juju deployer on my local machine during
> development.  The way to solve this issue might be very easy, still I can't
> manage it.
>
> The things I've done:
>
> 1. I've installed `juju-deployer` from source with `python setup.byinstall` command (running this command in folder fetched from `
> lp:juju-deployer`).
> 2. Then I removed juju-deployer package with all possible ways:  `sudo
> dpkg -r juju-deployer` , `sudo pip uninstall juju-deployer`.
> 3. And then I reinstalled it with `sudo apt-get install juju-deployer`
>
> After this steps I get following stack trace every time I run `juju
> deployer` command with valid options:
> https://gist.github.com/allomov/10327181
>
> What do you think about it? Did I missed something and it is easy to fix
> it or it would be better to recreate dev box (I'm working inside vagrant
> box).
>
> Thank you,
> Alex.
>