=== medberry is now known as Guest46324 === CyberJacob|Away is now known as CyberJacob === freeflying_away is now known as freeflying === freeflying is now known as freeflying_away === freeflying_away is now known as freeflying === freeflying is now known as freeflying_away [17:48] When trying to setup juju to work locally I get: WARNING unknown config field "$JUJU_HOME" $JUJU_HOME is commented out in ~/.juju/environments.yaml - any ideas? [18:09] cjohnston have you tried removing that line entirely? [18:10] no, assumed it would understand the comment [18:10] well typically it does as long as it's a valid comment in yaml [18:10] I can't really tell without seeing the file [18:11] hatch: removed it, still happening [18:11] one sec, let me clean it [18:12] https://juju.ubuntu.com/docs/config-local.html [18:12] cjohnston make a backup of your current environments.yaml and then `juju generate-config --show` [18:13] as per those docs [18:13] hatch: http://paste.ubuntu.com/6469924/ the relevant parts [18:14] hmm yeah that all looks good to me, I am guessing that there is something else in the file [18:14] I'd try to generate a raw config file to see if that works [18:17] http://paste.ubuntu.com/6469939/ [18:17] hatch: ^ [18:18] hmm I am totally out of ideas [18:18] cjohnston I suppose the only other thing I can offer would be to bootstrap with -v [18:19] it -may- give you more information [18:24] hatch: hrm.. I guess it somehow already had a bad bootstrap.. destroy-env and I am kinda back up and running [18:24] now a complaint about CA cert [18:24] ahh darn, well at least it's closer :) [18:25] :-) [18:25] thanks hatch [18:53] cjohnston np - curious, was it the -v which told you you had a problem or did you just try to destroy first? [18:53] -v [18:53] ahh great :) === freeflying_away is now known as freeflying