[06:22] <anrah> Hi,
[06:23] <anrah> As https://jujucharms.com/docs/devel/howto-privatecloud for 2.0 is still being rewritten is that Devel version something I can use to test 2.0 on my private openstack?
[07:48] <jamespage> junaidali, bbaqar: morning
[07:48] <jamespage> junaidali, so regarding xenial branches; we really don't need todo that any longer.
[07:49] <jamespage> the charm store does not injest from launchpad bzr branches any longer, you direct publish to the charm store, decoupling VCS from publication altogether
[07:49] <jamespage> are your trusty and xenial charm versions identical?
[07:50] <jamespage> if so we can use the series in metadata feature and just have a single charm version for both - this is what we do across all other openstack charms in master branch (that will be released this week).
[07:50] <junaidali> Hi jamespage, xenial charms have a few minor changes
[07:50] <jamespage> junaidali, is it possible to add that into the charm, rather than having two different charms?
[07:50] <jamespage> i.e. conditional code for xenial vs trusty?
[07:51] <jamespage> junaidali, we've found it much easier to support a single codebase for multiple releases, rather than having lost of differnent branches for different versions
[07:52] <junaidali> yes, we can do that.
[13:54] <SimonKLB> hey, anyone could tell me how to automatically attach a resource when running an amulet test?
[15:00] <holocron> "juju status" with lxd/local just hangs with no response, I've seen this before when lxd containers are not starting properly, but this does not seem to be the case now
[15:01] <holocron> what's my first course of action for debugging, or gathering enough info for a bug report?
[15:01] <holocron> "juju switch default" hangs, most juju commands are hanging
[15:01] <rick_h_> holocron: try adding --debug to the commands and see if anything jumps out
[15:02] <rick_h_> holocron: I thuoght there was a bug along those lines /me goes to look
[15:02] <holocron> rich_h_ thanks, yes that's obvious -- juju.api is looping on a dial to wss://x.x.x.x:17070/api
[15:03] <rick_h_> holocron: and are you able to reach that address?
[15:03] <holocron> i can ping it yes
[15:03] <holocron> it's a local lxd container, i'll exec bash into it
[15:03] <rick_h_> holocron: then perhaps the controller went down for some reason? can you ssh/connect to the controller and check the logs there?
[15:03] <rick_h_> holocron: maybe try to bounce jujud?
[15:04] <holocron> yeah, jujud seems to be thrashing a bit
[15:04] <holocron>  17330 root      20   0 49.690g 5.858g   7000 S   0.3 15.0 154:16.67 jujud
[15:05] <holocron> it's not listening for that wss connection
[15:06] <holocron> rick_h_ : jujud isn't a service it seems, should i restart the whole container, or is there a preferred method for just restarting the daemon?
[15:06] <rick_h_> holocron: sudo service juju<tab>?
[15:06] <rick_h_> holocron: let me look for the real name
[15:08] <holocron> yeah, i'm not finding any service for jujud
[15:09] <rick_h_> holocron: there you go, jujud-machine-0
[15:09] <holocron> ah thank you.. i guess the tab completion isn't working in lxc exec bash
[15:11] <holocron> rich_h_: were you able to find that bug? still hanging up on me here
[15:13] <rick_h_> holocron: not yet
[15:13] <rick_h_> holocron: did it restart for you?
[15:14] <holocron> rick_h_: okay, yeah it did restart, but i'm getting mongodb connection errors in the log
[15:14] <rick_h_> holocron: can you peek at the /var/log/juju/machinexxxx
[15:14] <rick_h_> holocron: ah ok, so let's try restarting that then as well
[15:14] <rick_h_> sudo service juju-db restart
[15:14] <rick_h_> and then re-kick jujud after the db is restarted and see what's up with that
[15:15] <rick_h_> holocron: is this on a laptop or something that's shutdown/back up often?
[15:15] <rick_h_> holocron: or some other system?
[15:15] <holocron> rick_h_ : it's running on a mainframe, it hasn't come down since it was working Friday night
[15:16] <holocron> Oct 10 15:16:23 juju-84a348-0 systemd[1]: Failed to start juju state database.
[15:18] <holocron> got a mongodb backtrace
[15:18] <rick_h_> holocron: ah ok. well that's starting to look like a root cause
[15:18] <rick_h_> holocron: and yea, exising bugs don't line up to this so treading new ground
[15:19] <holocron> par for the course for me :P
[15:19] <rick_h_> holocron: oh lucky you?
[15:19] <rick_h_> holocron: what's the traceback from mongo look like?
[15:19] <holocron> rick_h_: i'll paste it out in a moment
[15:22] <holocron> rick_h_: https://gist.github.com/vmorris/7750b8f9d3dfaa14238df39f7628ea3a
[15:23] <holocron> hmm, that doesn't have the trace in it :P
[15:23] <holocron> sec
[15:25] <holocron> rick_h_: please see revision 2 on that gist
[15:32] <vmorris> something called wiredtiger reporting an i/o error when attempting to read data
[15:36] <vmorris> i didn't run out of storage :/ using zfs on the localhost as per the normal setup
[15:36] <vmorris> there's really nothing out of the ordinary here except i'm running s390x arch
[15:38] <vmorris> let me trace back through the log and see if i can determine a first fault
[16:29] <vmorris> rick_h_: could this be related? https://gist.github.com/vmorris/f81217815059c6fc748eaba8cc1b5318
[16:30] <rick_h_> vmorris: sorry, issed you changed nick/continued the conversation
[16:31] <rick_h_> vmorris: wiredtiger is the mongodb engine
[16:31] <rick_h_> vmorris: looking at the gist
[16:31] <vmorris> rick_h_: apologies for the nick switch
[16:31] <rick_h_> vmorris: all good
[16:31] <rick_h_> vmorris: sorry, I'm not a mongodb expert to know how to decipher that
[16:32] <rick_h_> vmorris: please feel free to file a bug with the notes on arch, etc. It sounds like mongodb bit on something and that caused Juju to bail out on you.
[16:34] <vmorris> rick_h_: this seems to be the case, yeah. i've had the juju controllers flaking out on me a bunch over the past few weeks, but i've chalked it up to my fooling with things. i've reset to working clean state a bunch in the past few weeks and finally got to a good position to uncover a few things
[16:37] <bdx> mbruzek, lazyPower: sup sup
[16:39] <bdx> cory_fu: sup
[16:40] <bdx> lets say I want to re-gen certs, and re-render my nginx config when fqdn config is changed
[16:40] <bdx> would this be a good way of accomplishing ^ -> https://github.com/jamesbeedy/charm-documize/blob/master/reactive/documize.py#L200-L207 ?
[16:41] <bdx> if I remove line #136 -> https://github.com/jamesbeedy/charm-documize/blob/master/reactive/documize.py#L119-L136
[16:42] <bdx> If #136 is removed, would my charm be requesting a new cert every time the hook environment executes?
[17:24] <vmorris> arosales: ping https://bugs.launchpad.net/juju/+bug/1632030
[17:24] <mup> Bug #1632030: juju-db fails to start -- WiredTiger reports Input/output error <juju> <juju-db> <mongodb> <s390x> <juju:New> <https://launchpad.net/bugs/1632030>
[17:42] <Prabakaran_> Hello Team, Getting timeout issue while commissioning the node in MAAS 1.9, Logs are pasted in here  http://pastebin.ubuntu.com/23301741/ could somebody help me on this?
[17:45] <vmorris> Prabakaran_: have you confirmed that you've imported the boot images? https://maas.ubuntu.com/docs/install.html#import-the-boot-images
[17:48] <Prabakaran_> vmorris: I have imported images in the maas ui
[17:50] <vmorris> Prabakaran_: just have to ask, you did confirm that they were imported before trying to commission?
[17:51] <vmorris> It looks like you're trying to commission KVM virtual machines?
[17:51] <Prabakaran_> ya that was the 1st step i did before commissioning...
[17:51] <Prabakaran_> ya correct .. i am commissioning the vrish nodes
[18:17] <arosales> vmorris: thanks for the bug report :-)
[18:17] <vmorris> arosales: cheers :) i've torn the mess down and am about to redeploy the openstack-on-lxd bundle
[18:18] <arosales> Seems it goes into a defunct state
[18:19] <arosales> Will take a look and see if I can reproduce
[18:19] <vmorris> same
[18:19] <arosales> vmorris: Ubuntu 16.04 with updates I presume
[18:20] <vmorris> VERSION="16.04.1 LTS (Xenial Xerus)"
[18:23] <vmorris> arosales: I have a slightly modified version of the rabbitmq-server charm that i'm deploying as well to try and get more visibility into https://bugs.launchpad.net/charms/+source/rabbitmq-server/+bug/1563271
[18:23] <mup> Bug #1563271: update-status hook errors when unable to connect <landscape> <openstack> <rabbitmq-server (Juju Charms Collection):Confirmed> <https://launchpad.net/bugs/1563271>
[18:24] <arosales> Thanks for pitching on rabbit bug
[18:30] <vmorris> heh, sure i'll surface something if it works for me.. but it's purely selfish motivation =D
[19:04] <bdx> arosales: are you guys responsible for the percona-cluster charm?
[19:05] <bdx> beisner, arosales: this hardcoding is a piss off -> http://bazaar.launchpad.net/~openstack-charmers-next/charms/precise/percona-cluster/trunk/view/head:/hooks/percona_utils.py#L64
[19:05] <bdx> beisner, arosales: can we fix that hard coding of the pkgs so we can use latest version of percona?
[19:06] <beisner> hi bdx, what specifically are you needing to do?
[19:06] <arosales> Yes, specifically the openstack charmers
[19:07] <bdx> beisner: I need features that were introduced in 5.7
[19:07] <beisner> bdx, fyi, that charm's source of truth is https://github.com/openstack/charm-percona-cluster.  i have a pending request out to deprecate the old LP branches, which may not always be in sync with the latest bits.
[19:07] <bdx> beisned: aaah nice, thx
[19:07] <beisner> bdx, on which version of ubuntu ?
[19:07] <bdx> beisner: xenial
[19:07] <bdx> beisner: is there a problem with using percona repos by default?
[19:07] <bdx> https://www.percona.com/doc/percona-server/5.7/installation/apt_repo.html
[19:08] <beisner> bdx - we only test with ubuntu repos and the cloud archive pockets.
[19:09] <bdx> ahh
[19:09] <beisner> bdx, even yakkety has 5.6 atm so that's as bleeding edge as we get.  https://launchpad.net/ubuntu/yakkety/+source/percona-xtradb-cluster-5.6
[19:10] <beisner> bdx, all of that said, /me looks at that repo... :)
[19:10] <bdx> darn ... so -> http://paste.ubuntu.com/23304600/
[19:11] <bdx> ^ shows that 5.7 is xenial, just not for percona?
[19:11] <bdx> I see
[19:11] <bdx> ok
[19:11] <beisner> right, mysql might be ahead of percona-cluster packaging
[19:13] <bdx> beisner: percona-cluster charm has a config for 'source' and 'key', if the apt package for percona  wasn't hard coded,  I could then set 'source', 'key', and hypothetically 'package' and get the latest right?
[19:15] <bdx> I might just rig something up in my personal namespace for the time being - just needed the scoop on what the deal is so I know how best to move forward
[19:15] <bdx> beisner: thx
[19:15] <beisner> bdx, that hard-codedness is indeed a bit of crack, but was necessary crack whilst the packaging was in limbo around the vivid:wily timeframe.  with both wily and vivid now eol, we can pull that out after 16.10 release (too late in the feature freeze to do that now).  also i'd be all for making sure the charm can use the upstream repos.  but .. someone will have to get pretty clever to try to predictively know what the package name is going to be, given
[19:15] <beisner> that the version number is in the package name :-/
[19:22] <MrDanDan> hi guys
[20:09] <vmorris> hi
[21:24] <spaok> is there a python module or layer I can use to pull info from MAAS 2.0 in my charm? I want to get at the network space info
[21:28] <smgoller> Hey all, I'm trying to expand our juju-deployed openstack cluster, so I ran "juju add-machine". After it being stuck in a pending state for a number of minutes, I manually ssh'd into the machine and found that cloud-init had tried to run something involving 'curtin' and it failed because curtin wasn't installed. I also can't find any references to anything trying to install it. Has anyone run into a similar problem?
[21:30] <spaok> are you using custom images or something?
[21:33] <smgoller> nope
[21:34] <smgoller> so it looks like cloud-init is downloading some script from maas with a self-extracting archive that contains curtin inside it
[21:34] <smgoller> hm.
[21:53] <spaok> smgoller: never seen curtin fail to install in our deployments, I always thought it was baked into the ubuntu images
[23:15] <smgoller> i'm hesitant to blame juju on this yet. we've got some network wonkiness
[23:45] <spaok> smgoller: if you do apt update on that server do you get errors?
[23:45] <smgoller> it looks like intermittent dns resolution problems
[23:45] <smgoller> but the dns server is fine, so i think it's a layer 3 thing
[23:46] <smgoller> spaok: so I'm less concerned about juju at the moment and trying to make sure the infrastructure is solid
[23:46] <spaok> usually a good first step :)