[15:59] <x58> How can I debug why a juju run is not completing?
[16:08] <petevg> kwmonroe: here's the traceback I get when trying to deploy a xenial version of the zookeeper charm: http://paste.ubuntu.com/21019611/
[16:08] <petevg> It looks like it is a failure in the openjdk layer; it's looking for /etc/default/bigtop-utils, but that doesn't exist ...
[16:10] <kwmonroe> petevg: that ain't nary an openjdk layer failure.. openjdk doesn't need bigtop-utils.  it's gotta be a failure of zookeeper or the bigtop base layer.
[16:11] <petevg> Hmmm ... Zookeeper doesn't attempt to edit anything in place, though.
[16:11] <petevg> ... I think.
[16:11] <kwmonroe> yeah, it's coming from lib/charms/layer/apache_
[16:11] <kwmonroe> bigtop_base.py", line 239, in trigger_puppet
[16:12] <lazypower> x58 - you can juju debug-hooks application/#    which will put you in an interactive shell (just a plain ol root shell by default)
[16:12] <lazypower> it should trap that run stanza and give you an opportunity to debug
[16:13] <kwmonroe> petevg: i might have spoken too soon -- there is some java stuff that it's looking for during that re_edit_in_place.. i'll kick it around in just a few minutes.
[16:13] <petevg> kwmonroe: here's my branch, for reference: https://github.com/juju-solutions/bigtop/tree/zookeeper-bind-address
[16:13] <kwmonroe> cool, thx petevg
[16:13] <petevg> Did I specify the series correctly in metadata.yaml?
[16:14] <kwmonroe> yeah petevg -- that looks legit
[16:14] <x58> lazypower: Thans.
[16:14] <petevg> kwmonroe:  you're right about where it's coming from. Here's the line from the base layer:
[16:15] <petevg> http://paste.ubuntu.com/21020508/
[16:15] <petevg> kwmonroe: do we have any big data charms that we've actually deployed/tested on xenial?
[16:15] <kwmonroe> ah, right petevg.. so the question is now why isn't /etc/default/bigtop-utils present?  is zk trying to trigger_puppet before bigtop-base is available?
[16:18] <petevg> kwmonroe: Hmmm. Bigtop looks like it installed -- there's a bigtop.release directory in the ubuntu user's home dir.
[16:18] <petevg> etc/default/bigtop-utils isn't there, though.
[16:20] <kwmonroe> petevg: could it be the zookeeper deb in bigtop's repo doesn't correctly specify bigtop-utils as a prereq?  said differently, how does bigtop-utils get installed with a trusty deployment?  i don't see us specifically calling that out in the bigtop base layer.
[16:20] <petevg> kwmonroe: That sounds plausible (I don't see it explicitly installing it, either.)
[16:22] <petevg> kwmonroe: Yeah. If I apt install "bigtop-utils" and then run "juju resolved zookeeper/0", everything looks happier.
[16:22] <petevg> I think that I'm going to go ahead and cheat and just explicitly call "apt install bigtop-utils" in the charm for now, to get this done. I'll file a ticket w/ bigtop to get the package fixed.
[16:24] <kwmonroe> roger that petevg.. perhaps we can also work around with an explicit bigtop-utils entry in the base layer: https://github.com/juju-solutions/layer-apache-bigtop-base/blob/master/layer.yaml#L7
[17:25] <suchvenu> Hi
[17:26] <suchvenu> I am getting the following error when I deploy the charm http://pastebin.ubuntu.com/21028721/
[17:26] <suchvenu> and the juju status shows as "message: agent is lost, sorry! See 'juju status-history websphere-liberty/0'"
[17:27] <suchvenu> Can anyone help me with this ?
[17:28] <suchvenu> juju status history shows this : http://pastebin.ubuntu.com/21028908/
[17:39] <kwmonroe> suchvenu: it seems anastasia suggested trying juju-1.25.6 in bug 1465307, but i do not see that as released yet.
[17:39] <mup> Bug #1465307: 1.24.0: Lots of "agent is lost, sorry!" messages <canonical-bootstack> <landscape> <regression> <juju-core:New> <https://launchpad.net/bugs/1465307>
[17:39] <kwmonroe> anyone know when 1.25.6 is due?
[17:40] <lazypower> kwmonroe - its in proposed
[17:40] <lazypower> add-apt-repository ppa:juju/proposed
[17:42] <kwmonroe> ah, ack lazypower.. suchvenu if you want to try the proposed 1.25.6, do:
[17:42] <kwmonroe> sudo add-apt-repository ppa:juju/proposed && sudo apt update && sudo apt upgrade juju
[17:43] <suchvenu> ok kwmonroe
[18:07] <narindergupta> anyone knows how to connect juju to openstack (deployed through juju) i tried this URL https://blog.felipe-alfaro.com/2014/04/29/bootstraping-juju-on-top-of-an-openstack-private-cloud/
[18:07] <narindergupta>  but facing issues
[18:11] <lazypower> narindergupta - what issues are you encountering?
[18:12] <lazypower> narindergupta - we use juju driving a juju deployed openstack all the time internally with OIL and other efforts
[18:12] <narindergupta> lazypower, juju.cmd supercommand.go:429 failed to bootstrap environment: index file has no data for cloud {RegionOne http://10.5.1.83:35357/v2.0} not found
[18:12] <lazypower> ahh i  have seen this before but i dont recall the fix... one sec while I see if i can get someone to lend a hand.
[18:13] <narindergupta> lazypower, sure will be helpful. Also if you have the clear method explaining or script will be helpful?
[18:13] <lazypower> narindergupta - i think you have to build simplestreams, but i'm verifying that
[18:14] <narindergupta> lazypower, how to do that?
[18:14] <lazypower> i very well could be wrong, adn we have a lot of high profile folks out at the mid cycle sprint, so i may redirect you to the juju mailing list allowing them a chance to chime in
[18:15] <narindergupta> lazypower, zahra already posted this to mailing list. everyone says juju can not connect to cloud but manually i can do everything to cloud
[18:15] <narindergupta> lazypower, but any information will be helpful
[18:15] <lazypower> you bet, i'll do what i can to help. i've got your contact details, i'll e-mail you any information i can surface today
[18:16] <narindergupta> lazypower, sounds good to me thanks
[18:32] <magicaltrout> make it work lazypower !
[18:33] <lazypower> magicaltrout - working on it, its hard to do when there's no response from the SME's ;)
[18:33] <magicaltrout> hehe
[18:35] <petevg> kwmonroe: Hmmm ... looks like bigdata-utils being missing might be just the tip of the iceberg for Zookeeper on xenial. It looks like the Zookeeper xenial deb installs it in /usr/share/zookeeper rather than /usr/lib/zookeeper, and that screws up the puppet scripts :-/
[18:38] <kwmonroe> petevg: how are you specifying the xenial deb in your zk layer?
[18:39] <petevg> kwmonroe: I'm not. I'm just running puppet and letting it do its thing.
[18:39] <kwmonroe> petevg: did you alter the bigtop_repo_x86 layer opt?  or manually apt-add-repo?
[18:39] <petevg> Currently digging through puppet stuff to see if I can override the path ... I see a lot of instances of that zookeeper path being a defaul or hardcoded, though.
[18:39] <petevg> kwmonroe: again. Not doing anything manually. Just telling bigtop to do its thing.
[18:40] <kwmonroe> petevg: i bet i know what's happening.. i bet there's a zookeeper package in the xenial archives.  on the borked system, what does "dpkg -l | grep zoo" say?
[18:42] <petevg> kwmonroe: http://paste.ubuntu.com/21038468/
[18:42] <kwmonroe> petevg: how about "sudo apt-cache madison zookeeper"
[18:43] <petevg> kwmonroe: http://paste.ubuntu.com/21038664/
[18:43] <kwmonroe> thar she be petevg
[18:43] <petevg> So there is a package in universe.
[18:44] <petevg> Yeah. And it's newer, so that's why it's being grabbed, right?
[18:44] <kwmonroe> i'm not sure how the precedent is set
[18:44] <kwmonroe> but your thought seems reasonable.. bigger version wins
[18:45] <kwmonroe> so now petevg.. we need to figure out how to force the bigtop repo to win.  maybe a priority option we can set?
[18:45] <petevg> kwmonroe: Probably. Do you know where puppet calls apt/dpkg?
[18:46] <petevg> We either need to do some magic before that runs, or override it.
[18:48] <petevg> I think that I want to pin the package. I'm not sure that it's going to be easy to do so before bigtop installs zookeeper, but after it adds its repo. Digging into it now ...
[19:37] <kwmonroe> ok petevg, let's compare notes.. http://paste.ubuntu.com/21045756/
[19:38] <kwmonroe> petevg: one solution is to create an /etc/apt/preferences.d/file to force bigtop repos to take priority (as seen in above paste)
[19:39] <petevg> kwmonroe: Yep. That's pretty much what I found. Need to test it and make sure that it works before the repo is actually setup.
[19:45] <petevg> kwmonroe: thx for suggesting the wildcard -- covering the same case elsewhere makes sense.
[19:46] <kwmonroe> petevg: the pro is that presumably all zk deps would get prioritized too (or rather, all bigtop repo bits would).  the con is that there may be some old crusty deb in the bigtop repo that we really didn't want to take prescendent over the main archive.
[19:47] <petevg> True. I think that the pro outweighs the con, though.
[19:47] <kwmonroe> yeah, me too.  lest you're stuck managing deps in a preferences file till you simply die.
[19:47] <petevg> I'm sticking the file in a resource, reading it into Python, then writing it out, so we can do some parsing if it every becomes a big problem.
[19:48] <kwmonroe> word petevg.  perhaps think about using the bigtop_repo layer option (from bigtop base layer) as the url to use in the origin matcher.  it may not always be "bigtop-repos.s3.amazonaws.com".
[19:49] <petevg> kwmonroe: Good idea. Will do.
[19:50] <kwmonroe> in fact, it probably should never be that hard coded string, but whatever the hostname for the repo url may be.  surely there's some pythony thing to strip 'http://' and '/blah/foo' from a url and just leave the fqdn.
[19:56] <petevg> kwmonroe: bigtop_repo[7:].split("/")[0] should do it. Not pretty, but it works. :-)
[19:57] <magicaltrout> its okay
[19:57] <magicaltrout> kwmonroe hasn't written a pretty line of code in his life
[19:57] <kwmonroe> petevg: it's gonna get uglier too.. the layer option is "bigtop_repo-$(arch)"
[19:57] <petevg> Yep. I'm in the middle of writing that section of code right now :-)
[19:58] <kwmonroe> and petevg, what if somebody uses https or ftp?  that'll dork the 7th char.
[19:58] <kwmonroe> magicaltrout: all my code is handsome
[19:58] <petevg> This is why a lib is always nice :-)
[19:58] <magicaltrout> hehe
[19:59] <kwmonroe> dont we use urlparse in these bt charms?  surely that would do a fine parsing job
[19:59] <magicaltrout> urlparse
[20:00] <petevg> Here's an ugly function for you: http://paste.ubuntu.com/21048613/ (Going to test to verify that the approach works, and worry about making things prettier later.)
[20:00] <kwmonroe> magicaltrout: if you can't keep up, at least keep quiet
[20:00] <magicaltrout> *sob*
[20:00]  * magicaltrout finds more wine
[20:00] <kwmonroe> ;)
[20:01] <petevg> magicaltrout: thank you. urlparse is a good idea, to catch other stuff I haven't thought of.
[20:01] <kwmonroe> petevg: i like everything about that function except line 8
[20:02] <kwmonroe> that's like 92% approval from me
[20:02] <kwmonroe> which is pretty incredible
[20:02] <petevg> Excellent. I'll fix up line 8 with urlparse before review :-p
[20:02] <kwmonroe> :)  +1
[20:17] <petevg> kwmonroe: yay. Tests passed! Cleaning up code. PRs coming your way soon ...
[20:33] <x58> juju run --service myserver hangs forever and never seems to complete.
[20:36] <petevg> kwmonroe: PRs for you: https://github.com/juju-solutions/bigtop/pull/30  lazyPower had volunteered to review them, so feel free to sling it over to him if you run short on time :-)
[20:36] <petevg> (That PR links to the other two.)
[20:59] <kwmonroe> roger petevg, taking a gander ahora
[21:36] <zeestrat> Hey guys, what would you do if you'd need to deploy some none juju services on blank Ubuntu machines if you have an MAAS managed infra with some juju deployments already? Just commission machines in MAAS, use the ubuntu charm so you can manage it some what with juju and get some flexibility with lxd containers, or some other approach?
[21:37] <zeestrat> I see that the ubuntu charm is intended for testing and development, but is there anything inherently missing that I should look out for?
[21:42] <kwmonroe> petevg: "This breaks many things"  lol.  zk and bigtop-base PRs merged.  we'll let upstream marinate on their PR.
[21:45] <petevg> kwmonroe: Cool. Thank you :-)
[21:48] <kwmonroe> zeestrat: deploying 'ubuntu' seems a fine way to do what you want.  i don't know of anything missing that would make you say "oh, this is why it's test/dev only".  it's just a cloud-init ubuntu installation.
[21:49] <kwmonroe> zeestrat: and you do get the benefit of connecting stuff up to it.. anything that uses the juju-info relation can be attached to your 'ubuntu' charm units... stuff like ganglia for monitoring, etc
[22:42] <kwmonroe> petevg: fwiw, https://jujucharms.com/u/bigdata-dev/zookeeper/xenial/1 is your new hotness
[22:43] <petevg> kwmonroe: sweet! Thank you :-)
[22:44] <kwmonroe> not so fast petevg.. the bigtop_apt change in the zookeeper push now conflicts with your unit test PR :/  https://github.com/juju-solutions/layer-apache-bigtop-base/pull/28
[22:45] <kwmonroe> not a big deal, just wanted to knock you down a peg this fine tuesday afternoon ;)
[22:45] <petevg> kwmonroe: of course it does. Will fix it in the morning :-)
[22:45] <kwmonroe> cool - thanks, and have a good night!