[02:47] <tvansteenburgh> rsynnest: ping
[02:54] <rsynnest> tvansteenburgh: hey!
[02:54] <rsynnest> was the github outdated?
[02:54] <tvansteenburgh> hey, see my email?
[02:54] <tvansteenburgh> yeah, updating now...
[02:55] <rsynnest> awesome, thanks man
[02:56] <tvansteenburgh> rsynnest: my pleasure! just pushed the changes if you wanna have another go
[03:14] <rsynnest> tvansteenburgh: no luck :/
[03:14] <rsynnest> would running in a python virtualenv have any effect on the charm?
[03:16] <rsynnest> like maybe python dependencies aren't accessible?
[03:19] <tvansteenburgh> rsynnest: same traceback?
[03:21] <rsynnest> not sure, I'll check. It did fail on install hook
[03:28] <tvansteenburgh> rsynnest: if it's the same, while you're in debug hooks, try running `add-apt-repository -y ppa:chris-lea/node.js`, since that appears to be where it failed the first time
[03:41] <rsynnest>  add-apt-repository: command not found
[03:41] <rsynnest> both software-properties-common and python-software-properties are installed
[03:42] <tvansteenburgh> wha...
[03:45] <tvansteenburgh> apt-get install apt-file -y
[03:45] <tvansteenburgh> apt-file search add-apt-repository
[03:47] <rsynnest> dope, i forgot the debug-hook runs on the unit's machine
[03:47] <tvansteenburgh> :)
[03:47] <rsynnest> i have add-apt-repo local but not on the machine
[03:50] <rsynnest> that did the trick
[03:51] <rsynnest> XD
[03:51] <rsynnest> thanks for the help!
[03:51] <tvansteenburgh> so what did you have to do?
[03:51] <tvansteenburgh> install add-apt-repo?
[03:51] <rsynnest> just installed software-properties-common to the meteor machine
[03:52] <tvansteenburgh> okay, cool, i'll get the charm updated
[03:53] <tvansteenburgh> thanks for helping make the charm better rsynnest!
[03:54] <rsynnest> np, thanks for being so responsive
[03:54] <rsynnest> errr hang on
[03:54] <rsynnest> next hook is failing lol
[03:55] <tvansteenburgh> k, paste me a trace when you have it
[03:55] <rsynnest> how did you know it was the add-apt that was causing the issue?
[03:55] <tvansteenburgh> saw it in your traceback in the email
[03:55] <rsynnest> http://paste.ubuntu.com/9484186/
[03:57] <tvansteenburgh> hrm, did you run the install hook again after installing those deps?
[03:57] <rsynnest> yeah
[03:58] <rsynnest> im still in the same debug-hook shell
[03:58] <tvansteenburgh> `which mrt`
[04:02] <tvansteenburgh> rsynnest: what's the output of `which mrt`
[04:02] <rsynnest> oh, it returns nothing
[04:03] <rsynnest> wasn't sure if that was you thinking you were in termie :)
[04:03] <rsynnest> ls
[04:03] <tvansteenburgh> ha
[04:05] <tvansteenburgh> i'm not sure how install succeeded if we don't have that
[04:11] <rsynnest> ahhhh sorry
[04:11] <rsynnest> i re-ran install and it does fail at the end, i missed it
[04:11] <rsynnest> Unusable architecture: armv7l
[04:11] <rsynnest> Meteor only supports i686 and x86_64 for now.
[04:11] <rsynnest> dang
[04:12] <tvansteenburgh> doh!
[04:12] <tvansteenburgh> bummer :)
[04:12] <rsynnest> well, if anyone asks now you know
[04:13] <rsynnest> sorry for the wild goose chase :P
[04:13] <tvansteenburgh> np at all, it was helpful
[04:14] <tvansteenburgh> hope you stick around juju anyway!
[04:14] <rsynnest> welp, time to go bug the meteor folks ( ͡° ͜ʖ ͡°)
[04:14] <tvansteenburgh> hehe
[04:15] <tvansteenburgh> time for me to call it a night, cya around rsynnest
[04:15] <rsynnest> peace man, thanks again for the help
[04:15] <tvansteenburgh> you bet!
[09:18] <Saviq> hey all, I seem to have my mysql unit stuck in "installed" (and now in "dying" after trying to destroy it), what could I do to debug?
[09:20] <Saviq> forced the machine out, trying again
[09:28] <Saviq> so yeah mysql permanently gets into "installed" state for me
[09:28] <Saviq> oh now it ran!
[09:28] <Saviq> ok /me shuts up
[14:25] <jcastro> hey everyone, we're a video game: http://www.jujuandpeyo.com/
[15:53] <lazyPower> Congrats tvansteenburgh on your first charm promulgation since becoming a ~charmer!
[15:53] <lazyPower> may the users of meteor rejoyce in happyness as you have delivered their nectar
[15:53] <tvansteenburgh> \o/
[15:54] <lazyPower> mbruzek, marcoceppi_, dpb1, niedbalski ^ :)
[15:55] <mbruzek> cheers tvansteenburgh
[15:55] <niedbalski> tvansteenburgh, congrats!
[15:56] <ejat> congrats
[16:04] <jose> congratulations, tvansteenburgh!
[16:05] <lazyPower> oo sorry about the miss jose ;D i thought you were at uni
[16:06] <jose> lazyPower: told ya, I'm on vacation until April
[16:06] <lazyPower> nice
[16:10] <ejat> jose : have u finish the limesurvey charm test ?
[16:10] <jose> ejat: I'm poking on some critical stuff right now, but I did take a peek yesterday. looks like it's more than just that dependency, but I'll see what I can do
[16:12] <ejat> ok thanks :)
[17:45] <jose> marcoceppi_: hey, your seafile tests will depend on a fix that I'm pushing for review now
[17:48] <jose> marcoceppi_: also, the revq is not deleting some of the old closed/deleted MPs/charms
[18:39] <thebozz> Hey guys, we're trying to install Juju + Openstack on top of MAAS. The auto-install fails with this error log: http://pastebin.com/EWAwCEuN ... what could be wrong? We can SSH into our nodes.
[19:06] <aisrael> sebas5384: what platform are you using sshuttle on?
[19:08] <sebas5384> aisrael: using redir or iptables because sshuttle is too slow :(
[19:09] <aisrael> sebas5384: I have a workaround for sshuttle, but I've only tested it with OS X/Vagrant
[20:11] <thebozz> Hey guys, we're trying to install OpenStack on top of MAAS using the ubuntu tutorial (http://www.ubuntu.com/download/cloud/install-ubuntu-openstack).  We're currently on step 4, but it keeps failing with this error: http://pastebin.com/EWAwCEuN
[20:38] <lazyPower> thebozz: interesting - seems like possibly the keys didn't make during the bootstrap - have you retried teh provisioning? and is it consistent?
[20:39] <thebozz> lazyPower: we haven't reprovisioned. Yes, the error is constant. Should we try with a reprovision?
[20:39] <lazyPower> thebozz: i would give that a go and see if its intermittant failure, or if there are larger issues at play here.
[20:40] <thebozz> lazyPower: wait, you mean the SSH keys you configure on MAAS? We can connect to each node using SSH using the ubuntu user, so if that's what you meant then it's working fine.
[20:40] <lazyPower> thebozz: thats what i was referring to
[20:41] <thebozz> Hmmm. Then the keys are fine. What else could cause this? What user does juju try to connect to the nodes as?
[21:10] <lazyPower> thebozz: the ubuntu user
[21:11] <thebozz> lazyPower: so the login itself shouldn't be an issue either. I'm completely stumped with this one.
[21:11] <lazyPower> this is troublesome to me, as juju loads its own set of ssh keys with maas that it then uses to connect to the nodes.
[21:11] <lazyPower> thebozz: i'm not 100% familiar with the new 'autopilot' installer however
[21:12] <lazyPower> teh last time I did this, it was still a mostly manual process until you got to juju being bootstrapped.
[21:12] <lazyPower> thebozz: I would recommend pinging in #maas as well, someone may have some insight as to what the problem might be - but i beleive its after hours for them, quite a few of them are UK based.
[21:12] <thebozz> Still worth a try, though. Thanks!
[23:28] <dannf> is there some kind of 2 minute timeout during an install hook - e.g. between lines of stdout? i have a git clone that always fails around then, but if i juju ssh in, i can clone just fine