[04:02] <bdx> magicaltrout: just kick the juju machine agent process on that node
[04:04] <bdx> `sudo service jujud-machine-<#> restart` ?
[04:05] <kwmonroe> neclimdul: that's def a bug: https://git.launchpad.net/graylog-charm/tree/reactive/graylog.py#n81
[04:06] <kwmonroe> that handler needs to be "def blocked_mongo(elasticsearch):"
[04:10] <kwmonroe> arosales!!  it's 2 friggin machines!  how much smaller do you wanna go??
[04:10] <kwmonroe> (hey btw ;)
[04:11] <arosales> kwmonroe: howdy as you Texans say
[04:12] <kwmonroe> i'm doing whatever they say in philly through this weekend.  hook 'em eagles!
[04:12] <arosales> kwmonroe: I was mainly confirming k8-core was still the _recommended_ minimal
[04:13] <arosales> I am a fan of anyone playing against the Patriots
[04:13] <kwmonroe> yup arosales, k8s-core is it.
[04:13] <arosales> cool, thanks kwmonroe
[04:14] <arosales> enjoy Philly
[04:14] <arosales> skip the liberty Bell and visit some real history at the Rocky's bronze statue
[04:15] <kwmonroe> oh i'm not *in* philly.  i'm just talking like a philadelphian until the superbowl is over.
[04:15] <kwmonroe> so instead of "howdy", i'd say something like "cheese steak".
[05:34] <jhebden> neclimdul: make sure you're on the latest release. That bug was fixed previously.
[15:41] <bobeo> sadf
[15:41] <bobeo> o/
[15:42] <bobeo> having issues getting owncloud to install. so far ive tried several instances of owncloud deployment, and so far no dice. I keep getting a "hook failed: install" error. Is there a waay I can debug this issue?
[15:42] <magicaltrout> do juju debug-log for a start bobeo
[15:42] <magicaltrout> you'll get some error messages hopefully
[15:45] <bobeo> magicaltrout: ok so I see the log, btw, this is a godsend <3, I need to identify what it means by "apt key verifcation failed". Also, why is a canonical package repo pulling from opensuse?
[15:45] <bobeo> magicaltrout: also, it looks liek that even after that verification fails, it continues to download anyways. Does that mean its still working? I figured if it pushed an exit status 1, that it would fail outright?
[16:09] <magicaltrout> bobeo: i guess the repo updated their gpg keys or something, you'll have to file a bug https://bugs.launchpad.net/charms/+source/owncloud
[16:09] <magicaltrout> i'm not sure who owns that charm though, you could prod rick_h and see if he knows
[16:10] <rick_h> not sure who the owncloud folks are tbh
[16:10] <rick_h> been around a while though but not sure they've been vocal in irc/etc
[16:32] <kwmonroe> bobeo: looks like a new key was uploaded to the owncloud repo back in july of last year: http://download.opensuse.org/repositories/isv:/ownCloud:/community/xUbuntu_14.04/
[16:33] <kwmonroe> (btw, that's just opensuse hosting the project -- don't read too much into that, as it doesn't mean opensuse *packages* are trying to be installed)
[16:34] <kwmonroe> bobeo: but the charm has a specific key sum hard coded, see around line 40: https://api.jujucharms.com/charmstore/v5/owncloud/archive/hooks/install
[16:34] <kwmonroe> so i'm guessing that simply isn't the write shasum to verify the new key
[16:34] <kwmonroe> that said, there's a bug referencing an entirely new repo for more recent versions of OC:  https://bugs.launchpad.net/charms/+source/owncloud/+bug/1518009
[16:35] <mup> Bug #1518009: New official repository starting from 8.2 <owncloud (Juju Charms Collection):New> <https://launchpad.net/bugs/1518009>
[16:36] <kwmonroe> bobeo: but it doesn't seem like that charm is actively maintained -- no replies to those bugs in quite some time. like magicaltrout said, you could try to raise a new bug, or reach out directly to the maintainers listed at the top of the readme to see what's up with their charm.
[16:37] <magicaltrout> i saw your Bigtop PMC vote go through my inbox a couple of months ago kwmonroe, i forgot to say congrats when it got signed off, congrats!
 hi ..
 i used openstack-telemetry charms .. 2 services got problem (mongodb & neutron-gateway)  .. juju status output : http://paste.ubuntu.com/26506527/
 mongodb log output: https://paste.ubuntu.com/26506520/
 neutron-gateway: https://paste.ubuntu.com/26506512/
[16:37] <kwmonroe> thanks magicaltrout!
[16:37] <kwmonroe> it was a nice pay bump
[16:38] <rick_h> oooh, kwmonroe is celebrating today?
[16:38] <magicaltrout> ha, na i'm just slow to the party
[16:38] <kwmonroe> went from $0 to a very large value of 0.
[16:38] <rick_h> magicaltrout: lol, ok I had to go look and see it's Nov :P
[16:38] <rick_h> kwmonroe: but I didn't know so I'll be the last congrats to you :P
[16:39] <kwmonroe> heh, thx rick_h :)
[17:36] <ejat> how  to disable ipv6 in the charm?
[17:43] <kwmonroe> ejat: i don't think many (any?) charms let you disable host networking config.  they could, i suppose, by doing something with /etc/sysctl.conf, but i can't think of any that do.
[17:43] <kwmonroe> ejat: why do you want to disable it?
[17:43] <kwmonroe> also ejat, i didn't see any errors from mongo in your status or paste above.
[17:44] <kwmonroe> the neutron-gateway seems to be trying to add an unknown interface (eno2) to the br-ex bridge.
[17:46] <kwmonroe> that stuff looksl ike it's coming from the openstack charmhelpers code.  maybe beisner can point you to a troubleshooter?  (line 5416 here https://paste.ubuntu.com/26506512/)
[17:49] <beisner> seems like faulty config being fed into the charm.   ‘juju config neutron-gateway’  output will be helpful to see.
[17:53] <bobeo> kwmonroe: magicaltrout is it possible for us to take over that charm? Or would we need to build another charm for it? we use it heavily as part of our project, so we dont mind mantaining it as a way of contributing back
[17:55] <kwmonroe> bobeo: you bet you can take it over!  i took a look for other owncloud charms and found that the illustrious bdx has a better version: https://github.com/jamesbeedy/layer-owncloud
[17:56] <kwmonroe> bobeo: if you are going to go with a hostile takeover, i'd recommend starting from there ^^
[17:56] <kwmonroe> note that sucker unfortunately doesn't deploy out-of-the-box because of some new packaging in v10, but i did just verify it works if you set the repo to deploy v9.  here are some more deats on that: https://github.com/jamesbeedy/layer-owncloud/issues/1
[17:57] <bobeo> kwmonroe: I actually tried that one, and that was the one we were using before, it didnt work either. but yea, a hostile takeover would be nice, but can we do a "beerstiletakeover" instead? I mean, its bdx. Who doesnt love bdx?
[17:57] <bobeo> kwmonroe: oooh! that explains a lot!
[18:00] <bobeo> kwmonroe: Whats the best way to modify the config.yaml? As I understand it, it doesnt pull that until you execute the deploy command.
[18:01] <bobeo> kwmonroe: from what I understand, id have to start with: juju deploy cs:~jamesbeedy/owncloud-4 ; and then where woudl I go to modify the config.yaml file, and I assume to use sed as a method to swap to the v9?
[18:03] <kwmonroe> easy breezy bobeo... juju deploy with a --config yaml.  like this:
[18:03] <kwmonroe> $ cat test.yaml
[18:03] <kwmonroe> owncloud:
[18:03] <kwmonroe>   install_sources: |
[18:03] <kwmonroe>     - "deb http://download.owncloud.org/download/repositories/9.0/Ubuntu_16.04/ /"
[18:03] <kwmonroe> $ juju deploy ~jamesbeedy/owncloud --config test.yaml
[18:03] <bobeo> kwmonroe: 8O
[18:04] <bobeo> kwmonroe: For surely, as he hath shown me the light, I see for the first time.
[18:04] <kwmonroe> ha!
[18:04] <kwmonroe> i do what i can for beerstiletakeoverers
[18:19] <bobeo> kwmonroe: Ok, so to the next level, id like to do this for several packages, minecraft, (I know, I cant help it), owncloud, and gitlab for now, with pubshot, and several others in the near future. Also, I would love to know, is there any real difference between doing it with xenial, or precise for instance? If so, I wouldnt mind working to push several other packages from older versions like precise and trusty to xenial.
[18:20] <rick_h> bobeo: the big thing that hit most software going from precise to xenial and such is that there was a move from the upstart init system to systemd. So those init scripts/etc need to be handled.
[18:20] <bobeo> kwmonroe: feed a bobeo a fish, turn him into Gollum, teach a bobeo to fish, turn him into Lord Bobeo, Conqueror of Depricated Packages
[18:21] <kwmonroe> nah bobeo, don't let rick_h scare you.  xenial is pretty much just precise with 4 years of extra linux stuff on top.
[18:22] <kwmonroe> on the real though, huge +1 for refreshing any precise/trusty charms for xenial.  for gitlab, you might want to check out magicaltrout's (way better) rev:  https://jujucharms.com/u/spiculecharms/gitlab-server/8
[18:23] <kwmonroe> in fact, magicaltrout, do you think we should replace https://jujucharms.com/gitlab/ with your gitlab-server?
[18:32] <kwmonroe> rick_h: you still logging tips-n-tricks?  if so, i've got 3 that have come up recently:
[18:32] <kwmonroe> - if 'juju remove-[application|unit]' fails, 'juju resolved --no-retry' until it works
[18:32] <kwmonroe> - dont want to 'show-action-output' later, use 'juju run-action --wait' instead
[18:32] <kwmonroe> - need to change default charm config, use 'juju deploy foo --config' with a custom yaml
[18:34] <magicaltrout> you know your kids control the music too much when your "Top Tracks of 2017" on spotify includes 2 frozen tracks.....
[18:34] <magicaltrout> I don't mind kwmonroe, i still need to get around to exposing more of the fun stuff, but it does the job at the moment
[18:35] <kwmonroe> you know you're getting old when "alexa, play my programming staion on pandora" plays friggin NPR News!  i almost threw her across the room.
[18:36] <magicaltrout> lol
[18:36] <kwmonroe> then i thought, maybe it's not alexa, maybe it's pandora... and then i thought, oh no, maybe it's me!!
[18:50] <zeestrat> Speaking of refreshing old charms, rick_h, any news on getting some community curation tools in the store? It would help folks find which charms are preferred and which need some love and care.