=== kadams54 is now known as kadams54-away === kadams54-away is now known as kadams54 [00:52] jose: how can it be done in the CLI? [00:53] oh, juju-git-deploy. I had no idea! === kadams54 is now known as kadams54-away === scuttle|afk is now known as scuttlemonkey === scuttlemonkey is now known as scuttle|afk === kadams54-away is now known as kadams54 === scuttle|afk is now known as scuttlemonkey === scuttlemonkey is now known as scuttle|afk === scuttle|afk is now known as scuttlemonkey [02:51] 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] ah shizzle... Installing juju-git-deploy has messed up my juju-quickstart command [02:55] ImportError: No module named parse [02:55] :( [02:58] mmm... purging juju and resinstalling didn't help [03:04] #@!$ [03:05] I guess git-deploy needing pip3 to install means it needs Python3, while Juju apparently needs Python << 2.8... [03:06] leads to install messed up [03:06] :( [03:12] ah, okay... maybe juju/unstable ppa will sort this out [03:13] nope [03:25] looks like only quickstart is broken === kadams54 is now known as kadams54-away [07:21] 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] how can I get my session to stop at the hook if "exit 1" doesn't work [07:22] ? === CyberJacob|Away is now known as CyberJacob === CyberJacob is now known as CyberJacob|Away === CyberJacob|Away is now known as CyberJacob === erkules_ is now known as erkules === CyberJacob is now known as CyberJacob|Away === CyberJacob|Away is now known as CyberJacob === kadams54 is now known as kadams54-away === rogpeppe2 is now known as rogpeppe [16:36] jumpkick: try 'exit 225' [16:36] or something that's not 0 [16:37] higher then 1, okay I'll try that [16:38] jose, will it continue to the next hook regardless of the error state while in debug hooks? [16:39] jumpkick: it shouldn't - should put the unit in error state [16:39] that's what I figured [16:39] ok cool [16:56] jose: "exit 225" takes me to the next hook... it's busted on my system [16:57] jumpkick: wat. let me bootstrap real quick and try this myself [16:57] 1.20.13-utopic-amd64 is my juju version [17:00] ack [17:08] exit 1 does give an error state here, huh [17:08] jumpkick: can I suggest moving that variable to the config-changed hook? [17:12] jose: did I miss anything? my X just died [17:13] jumpkick: I mentioned that it's working good here... I was suggesting moving that config variable setup to config-changed [17:13] or if unset, create a sentinel file [17:13] 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] otherwise, it leaves the sentinel file untouched for the next go-round [17:14] ok, I'll see if I can get that going [17:19] cool :) [17:26] 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] is it the same bugs 1330553 [17:26] Bug #1330553: Align quickstart to the latest HP Cloud configuration options [17:26] ? [17:33] ejat: let me check [17:34] ejat: https://bugs.launchpad.net/juju-core/+bug/1374253 [17:34] Bug #1374253: hpcloud: index file has no data for cloud on region-b.geo-1

[17:35] it's the same as that one, can you please try changing to another region? [17:35] otoh, I would personally recommend AWS vs HPCloud, since it's way faster [17:39] jose: when I google "juju sentinel file" I get nothing... where can I find docs for it? [17:40] jumpkick: in which language are you writing your charm? [17:43] the charm is written in bash [17:45] ok, so you can do 'touch .sentinelnamehere' [17:45] and then, in the other hook, if [ -f .sentinelnamehere ]; then [17:45] not sure if you get it [17:48] 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] jumpkick: if you do 'juju set config=value', the config-changed hook will run [18:07] jose: cool, how can I get the install hook to run again [18:07] jumpkick: call it explicitly from the config-changed hook [18:07] call 'hooks/install' [18:08] ok, I guess that will work [18:08] thanks, I'll just work around it like that for now [18:09] awesome [18:09] lemme know how it goes === kadams54 is now known as kadams54-away === CyberJacob is now known as CyberJacob|Away