[00:02] <hazmat>  argh.. hotspot down to edge networking
[00:02] <hazmat> fail
[01:29] <jimbaker> hazmat, i'm trying to ssh into the local lxc containers with juju ssh. but i'm getting a pw prompt. looking at the code, i would expect it to just enable me to use my public key. what am i missing here?
[02:20] <hazmat> jimbaker, it should use your key
[02:21] <hazmat> jimbaker, although i had a minor accident today where i tried to ssh into the container from a root shell.. it needs to be the shell of the user who bootstrapped
[02:21] <hazmat> SpamapS, are you going to the wikipedia hack days in nola?
[02:22] <hazmat> i was just considering going down there
[02:25] <jimbaker> hazmat, ok, it's not working for me then. i'm using  local-origin-passthrough however
[02:25] <jimbaker> does that depend on some other branches?
[02:25] <hazmat> jimbaker, hmmm. let me push my latest
[02:25] <hazmat> jimbaker, that's the one i'm working against
[02:25] <jimbaker> hazmat, ok
[02:25] <hazmat> i gave up on my last attempt after my hotspot switched to edge
[02:26] <hazmat> although i was definitely able to ssh into my container
[02:27] <hazmat> jimbaker, looks like the latest is pushed
[02:27] <jimbaker> hazmat, definitely annoying that, although i find it's more of a transitory thing - maybe 5 min. assuming a place w/ a normal good signal
[02:27] <hazmat> jimbaker, i started putting the customize script output into the data-dir under units
[02:27] <jimbaker> hazmat, i was trying the latest
[02:28] <hazmat> that's what setups the container pretty much.. there's lots of logs on disk in the data-dir .. machine agent, container logs, customize script logs
[02:28] <hazmat> jimbaker, where you doing it from a root shell?
[02:28] <jimbaker> hazmat, no, just letting it ask for sudo as usual
[02:29] <hazmat> jimbaker, you can poke at the constructed container to see if the key is there its under /var/lib/lxc
[02:29] <hazmat> there should be an authorized key file  under /home/ubuntu/.ssh
[02:30] <jimbaker> hazmat, it's there
[02:30] <hazmat> i'm definitely able to login
[02:31] <hazmat> via ssh against the ubuntu user
[02:31] <jimbaker> hazmat, yeah, that's what it was prompting me for
[02:31] <hazmat> jimbaker, how are you doing ssh? using juju?
[02:31] <jimbaker> hazmat, yes
[02:31] <jimbaker> juju ssh wordpress/0, usual stuff
[02:31] <hazmat> ah.. i've been doing ssh by hand
[02:31]  * hazmat tries juju ssh
[02:32] <jimbaker> hazmat, i don't know enough about lxc, so i've been using the tool here ;)
[02:32] <hazmat> jimbaker, dig @192.168.122.1 container-name
[02:32] <hazmat> will give the ip address
[02:32] <hazmat> jimbaker, your actually farther than  i am atm, i haven't gotten the unit agent running (which means no juju ssh)
[02:33] <hazmat> i committed and pushed the fixes, but wasn't able to do a final run, due to lack of networking
[02:33] <hazmat> trying again
[02:33] <jimbaker> hazmat, i really was just tried juju ssh 0 in this case
[02:33] <hazmat> jimbaker, you can't do that
[02:33] <hazmat> i mean you can
[02:33] <hazmat> but its not what you think
[02:33] <jimbaker> yeah, that makes sense
[02:33] <hazmat> jimbaker, juju ssh 0
[02:33] <hazmat> is to login into a machine
[02:34] <hazmat> but all the units are on localhost
[02:34] <jimbaker> exactly
[02:34] <hazmat> one machine
[02:34] <hazmat> so its rather pointless and we don't mess with the host user's authorized keys in their home directory
[02:34] <jimbaker> i think the more relevant thing is the data-dir
[02:34] <jimbaker> at least i might see something
[02:34] <hazmat> so that won't work unless you've explicitly set it up
[02:35] <jimbaker> basically none of the service units start, just like your experience
[02:38] <hazmat> jimbaker, are you doing this juju-origin set?
[02:38] <hazmat> w/
[02:38] <jimbaker> hazmat, i tried, that didn't work
[02:38] <jimbaker> so now, no
[02:56] <hazmat> jimbaker, yeah.. ppa should work
[02:56] <hazmat> jimbaker, except it fails because of the protocol version increment, but the unit agents are running with it
[02:56] <hazmat> i'm still debugging why they don't come up with juju-origin
[02:56] <hazmat> although at this point, its time for a weekend
[02:59] <jimbaker> hazmat, sounds like a reasonable decision to me too! enjoy
[03:42] <hazmat> bcsaller, have you ever seen the pty allocation error
[03:42] <hazmat> it keeps coming up for me, very annoying.. basically needs a reboot
[03:42] <bcsaller> I've never gotten it, no
[03:55] <_mup_> juju/local-origin-passthrough r416 committed by kapil.thangavelu@canonical.com
[03:55] <_mup_> add python-yaml dep for branch installs, and switch address map s/lxc/local
[03:57] <hazmat> chr
[04:08] <hazmat> all working now, nice
[04:23] <_mup_> juju/unit-info-cli r422 committed by kapil.thangavelu@canonical.com
[04:23] <_mup_> missing bin/unit-get
[04:42] <_mup_> Bug #863816 was filed: We need a cross-provider way to allow units to get pub/priv address info <juju:In Progress by hazmat> < https://launchpad.net/bugs/863816 >
[16:49] <_mup_> Bug #864164 was filed: Must complain if charm hooks aren't executable <juju:New> < https://launchpad.net/bugs/864164 >