[00:52] <jrwren> jose: how can it be done in the CLI?
[00:53] <jrwren> oh, juju-git-deploy. I had no idea!
[02:51] <jumpkick> jrwen, if you are not an experienced python user, you'll need to install PIP3 on 14.10 - I wrote a quick ticket w/ the steps @ https://github.com/frankban/juju-git-deploy/issues/4
[02:55] <jumpkick> ah shizzle...  Installing juju-git-deploy has messed up my juju-quickstart command
[02:55] <jumpkick> ImportError: No module named parse
[02:55] <jumpkick> :(
[02:58] <jumpkick> mmm... purging juju and resinstalling didn't help
[03:04] <jumpkick> #@!$
[03:05] <jumpkick> I guess git-deploy needing pip3 to install means it needs Python3, while Juju apparently needs Python << 2.8...
[03:06] <jumpkick> leads to install messed up
[03:06] <jumpkick> :(
[03:12] <jumpkick> ah, okay... maybe juju/unstable ppa will sort this out
[03:13] <jumpkick> nope
[03:25] <jumpkick> looks like only quickstart is broken
[07:21] <jumpkick> I'm having some trouble with my debug-hooks...  seems "exit 1" is not sending the unit to back to error state, rather it's moving to the next stage.  If I put "exit 1" for all of them, at the end my unit ends up in started state
[07:22] <jumpkick> how can I get my session to stop at the hook if "exit 1" doesn't work
[07:22] <jumpkick> ?
[16:36] <jose> jumpkick: try 'exit 225'
[16:36] <jose> or something that's not 0
[16:37] <jumpkick> higher then 1, okay I'll try that
[16:38] <jumpkick> jose, will it continue to the next hook regardless of the error state while in debug hooks?
[16:39] <jose> jumpkick: it shouldn't - should put the unit in error state
[16:39] <jumpkick> that's what I figured
[16:39] <jumpkick> ok cool
[16:56] <jumpkick> jose: "exit 225" takes me to the next hook...   it's busted on my system
[16:57] <jose> jumpkick: wat. let me bootstrap real quick and try this myself
[16:57] <jumpkick> 1.20.13-utopic-amd64 is my juju version
[17:00] <jose> ack
[17:08] <jose> exit 1 does give an error state here, huh
[17:08] <jose> jumpkick: can I suggest moving that variable to the config-changed hook?
[17:12] <jumpkick> jose: did I miss anything?  my X just died
[17:13] <jose> jumpkick: I mentioned that it's working good here... I was suggesting moving that config variable setup to config-changed
[17:13] <jose> or if unset, create a sentinel file
[17:13] <jose> then, when config-changed is run, if it finds the sentinel file and the variable set, it configures and deletes the sentinel file
[17:14] <jose> otherwise, it leaves the sentinel file untouched for the next go-round
[17:14] <jumpkick> ok, I'll see if I can get that going
[17:19] <jose> cool :)
[17:26] <ejat> im facing this issue : ERROR cannot start bootstrap instance: index file has no data for cloud {az-1.region-a.geo-1 https://region-a.geo-1.identity.hpcloudsvc.com:35357/v2.0/} not found
[17:26] <ejat> is it the same bugs 1330553
[17:26] <mup> Bug #1330553: Align quickstart to the latest HP Cloud configuration options <juju-quickstart:Fix Released by frankban> <https://launchpad.net/bugs/1330553>
[17:26] <ejat> ?
[17:33] <jose> ejat: let me check
[17:34] <jose> ejat: https://bugs.launchpad.net/juju-core/+bug/1374253
[17:34] <mup> Bug #1374253: hpcloud: index file has no data for cloud on region-b.geo-1 <bootstrap> <hp-cloud> <juju-core:Triaged> <https://launchpad.net/bugs/1374253>
[17:35] <jose> it's the same as that one, can you please try changing to another region?
[17:35] <jose> otoh, I would personally recommend AWS vs HPCloud, since it's way faster
[17:39] <jumpkick> jose: when I google "juju sentinel file" I get nothing...  where can I find docs for it?
[17:40] <jose> jumpkick: in which language are you writing your charm?
[17:43] <jumpkick> the charm is written in bash
[17:45] <jose> ok, so you can do 'touch .sentinelnamehere'
[17:45] <jose> and then, in the other hook, if [ -f .sentinelnamehere ]; then
[17:45] <jose> not sure if you get it
[17:48] <jumpkick> hmm...  now I get what you were saying, but it isn't going to work...   once I exit all my debug-hooks I end up with a unit that's in "started" state (even though its unconfigured)...  juju won't let me do a "resolved -r" on a started unit to redo the config
[18:06] <jose> jumpkick: if you do 'juju set config=value', the config-changed hook will run
[18:07] <jumpkick> jose: cool, how can I get the install hook to run again
[18:07] <jose> jumpkick: call it explicitly from the config-changed hook
[18:07] <jose> call 'hooks/install'
[18:08] <jumpkick> ok, I guess that will work
[18:08] <jumpkick> thanks, I'll just work around it like that for now
[18:09] <jose> awesome
[18:09] <jose> lemme know how it goes