[00:21] <smgoller> thumper the endpoint is set to similar to the example: http://my.mass.server/MAAS
[00:22] <thumper> hmm...
[00:22] <thumper> can I get you to put a slash on the end?
[00:22] <thumper> it shouldn't matter, but might
[00:22] <smgoller> this is the error:
[00:22] <smgoller> hold on let me pastebin it
[00:23] <smgoller> thumper http://paste.ubuntu.com/23524903/
[00:23] <smgoller> gut feeling is the slash won't matter, but i can try it if you like
[00:23] <thumper> nuh
[00:23] <thumper> that's fine
[00:24] <thumper> no idea why that is happening to be honest
[00:24] <thumper> it shouldn't
[00:24] <thumper> can you hit the 2.0 api endoint without juju in the way?
[00:24] <smgoller> yes
[00:25] <smgoller> thumper let me reverify that, actually
[00:25] <thumper> from the controller machine?
[00:26] <smgoller> juju and mass box are the same
[00:26] <smgoller> maas box that is
[00:28] <smgoller> thumper  hitting http://maas.goller.lan/MAAS/api/2.0/version/ works fine from both maas/juju machine and another machine on the network
[00:29] <smgoller> oh
[00:29] <smgoller> hm.
[00:29] <thumper> ?
[00:29] <smgoller> n/m for some reason I was thinking the controller being boostrapped couldn't talk to the maas box, but it's being bootstrapped from the maas box :)
[00:30] <smgoller> and it's definitely ssh'ing into it
[00:30] <smgoller> so it successfully launches the host via maas, right now it's installing the machine agent
[00:30] <rick_h> smgoller: does the 1.0 api version exist on 2.0?
[00:31] <rick_h> smgoller: e.g. can you take that url and hit it successfully as does the 1.0 api version say it's maas 2.0?
[00:31] <smgoller> not any more apparently. If you hit 1.0 it says it's been removed.
[00:31] <rick_h> smgoller: what's the version response from that call above?
[00:31] <rick_h> e.g. what does maas say its version is?
[00:32] <smgoller> 2.1.1+bzr5544-0ubuntu1
[00:32] <rick_h> ok, so this is a dev version of maas? they just got 2.1.1 out today right?
[00:32] <smgoller> er
[00:33] <smgoller> it's maas-stable repo
[00:33] <rick_h> ok, the +bzr/etc made me suspect it as a dev version but ok
[00:34] <rick_h> I know that froboware was having issues with 2.1.1 and juju trunk, but it was in getting vmaas machines working vs bootstrap/api version I thought I understood it to be
[00:34]  * rick_h wonders if they yanked something and we've not noticed it yet. I just sent a request to QA to update our maas to 2.1.1 today based on the new release
[00:36] <rick_h> smgoller: I'll have to spin up a vm and try the latest maas and see what I can see
[00:36] <rick_h> thumper: if you get a sec I wanted to chat please
[00:38] <thumper> hmm...
[00:38] <thumper> rick_h: hey
[00:38] <smgoller> rick_h: awesome. thanks!
[00:38] <rick_h> thumper: can I steal 15min ?
[00:38] <thumper> rick_h: sure
[00:38] <rick_h> smgoller: heh don't thank me yet, going to take a sec
[00:38] <rick_h> thumper: do you have a bluejeans or something you use?
[01:05] <smgoller> rick_h: you're looking into it, that's all that counts.
[01:24] <rick_h> thumper, so I can't find any examples of us parsing this complicated version string on the gomaasapi code: https://goo.gl/uKxsbE
[01:24] <rick_h> thumper: my guess is that the version checker is failing to parse, returning an error, and that's turning into an error that it's not a 2.0 supported version and it falls back to 1.0
[01:25]  * thumper looks
[01:25] <rick_h> thumper: but I don't follow that parser code well enough for the problem to jump at me and the controller_test.go code doesn't have anything testing it's parsing I'd expect to see.
[01:25] <thumper> it just unmarshalls the json
[01:26] <rick_h> thumper: any chance there's a fast way to test that method against the version string 2.1.1+bzr5544-0ubuntu1 ?
[01:26] <thumper> paste me the version string
[01:27] <rick_h> thumper: https://goo.gl/RQn9Im is what I think is failing
[01:27] <rick_h> thumper see line above, the 2.1.1+bzr...
[01:27] <rick_h> "version": "2.1.2+bzr5555-0ubuntu1" is my json output
[01:28] <thumper> that isn't valid json
[01:28] <rick_h> thumper: no, you want the full json?
[01:28] <thumper> yes
[01:28] <rick_h> thumper: http://104.199.217.13/MAAS/api/2.0/version/
[01:28]  * thumper pokes the code
[01:30] <thumper> no... that should be fine
[01:31] <rick_h> hmm, ok then. No idea. I can verify that you're right. It tries 2.0 first, and the error smgoller is seeing is when it fails to find a valid version and that version is put together by parsing that output.
[01:31] <thumper> smgoller: can you try bootstrap with --debug?
[01:31] <thumper> smgoller: that will at least get the line that is failing the 2.0 check to be logged
[01:31] <rick_h> smgoller: +1 be curious if that debug line about "read version failed:" comes out in there
[01:31] <thumper> rick_h: that isn't what is done
[01:32] <thumper> rick_h: the 2.0 endpoint is hit, and the only thing that is looked at in that response is the capabilities array
[01:32] <rick_h> thumper: ? /me is reading it wrong? readVersionFailed is checking it parsed the json response?
[01:32] <thumper> parse just hits the url and parses the json
[01:32] <thumper> version is the path
[01:32] <thumper> not the field name
[01:33] <rick_h> thumper: understand, sorry. I just mean the output of version. in that readAPIVersion
[01:33] <thumper> it would say 2.0
[01:41] <rick_h> so bootstrap against this maas with 2.0.0 works (well it complains about lack of machines but gets that far)
[01:41]  * rick_h upgrades to devel ppa
[01:41] <rick_h> smgoller: where did you get your juju from?
[01:42]  * rick_h smacks head for not upgrading juju 2 vs just juju
[01:45] <rick_h> smgoller: ok, I can't replicate with the 2.1 beta1 either. I have to say to check your url and your credentials in .local/share/juju/credentials.yaml  and clouds.yaml
[01:46] <rick_h> I don't think it's an auth problem, I get 01:46:03 ERROR cmd supercommand.go:458 Authorization Error: Invalid API key.
[01:46] <rick_h> if I change my oauth token...
[01:48]  * rick_h waits for bootstrap to timeout with a bad url for the maas endpoint...
[01:49] <rick_h> boom, here we go I bet: 01:49:22 DEBUG maas controller.go:80 read version failed: &errors.Err{message:"", cause:(*url.Error)(0xc82044a000), previous:(*errors.Err)(0xc82040c0a0), file:"github.com/juju/gomaasapi/controller.go", line:794}
[01:50]  * rick_h now waits for v1.0 to time out
[01:51] <rick_h> boom! {Get http://104.199.217.130/MAAS/api/1.0/version/: dial tcp 104.199.217.130:80: getsockopt: connection timed out}])
[01:52] <rick_h> ok, so that's what it is. failure to reach the maas server at all
[01:52] <rick_h> thumper: smgoller ^
[01:52] <rick_h> the bug I'll file from here is that we need to output to the user when we fail to connect/find v2.0 so that's much more obvious in the output to the user
[01:52] <rick_h> because you can't tell "cannot communicate with maas" vs "wtf are you looking at the 1.0 api url?"
[01:53] <thumper> huh
[01:53] <thumper> interesting
[01:53] <rick_h> https://pastebin.canonical.com/171681/ for full output
[01:56] <rick_h> smgoller: filed https://bugs.launchpad.net/juju/+bug/1644395 on your behalf
[01:56] <mup> Bug #1644395: failure to connect to maas endpoint looks the same as wrong maas version <observability> <usability> <juju:Triaged> <https://launchpad.net/bugs/1644395>
[01:57]  * rick_h stops working now...
[03:56] <viswesn> Do juju bootstrap output can be send to log file? rather than stdout or stderr?
[03:59] <viswesn> I am writing juju-ci-tool and I want the output of juju bootstrap redirected to a file
[04:46] <hallyn> juju won't shut up: Nov 24 05:39:09 sergeh2 mongod.37017[16252]: Thu Nov 24 05:39:09.595 [conn26] command juju.$cmd command: { getLastError: 1, j: true } ntoreturn:1 keyUpdates:0  reslen:83 111ms
[04:54] <viswesn> redirecting stdout and stderr fails on juju-ci-tools; - http://paste.ubuntu.com/23525597/
[04:54] <viswesn> how to overcome this issue
[05:48] <Ankammarao> Hi All
[05:49] <Ankammarao> i am new to terms
[05:49] <Ankammarao> can any tell me how to create terms or push terms
[07:04] <lazyPower> Ankammarao: https://jujucharms.com/docs/2.0/developer-terms
[07:07] <Ankammarao> thanks lazyPower, but charm push-term  is not working for my machine
[07:08] <Ankammarao> giving error like ERROR unrecognized command: charm push-term
[07:08] <lazyPower> Ankammarao: do you have the charm package installed?
[07:08] <Ankammarao> yes installed
[07:09] <lazyPower> Ankammarao: did you install via the snap?
[07:10] <Ankammarao> yes
[07:10] <viswesn> I am getting always juju version - 2.1-beta2-xenial-amd64 rather than stable version; I also ran - sudo add-apt-repository ppa:juju/stable
[07:10] <Ankammarao> snap has installed at /snap/bin/charm
[07:11] <viswesn> how to get stable rc3 version of juju
[07:11] <lazyPower> Ankammarao: would you mind filing a bug here? https://github.com/juju/charmstore-client/issues
[07:11] <Ankammarao> ok sure
[07:15] <viswesn> how to upgrade to juju2.0 rc3 version from my current juju version 2.1-beta2-xenial-amd64
[08:20] <kjackal> Good morning Juju world!
[08:32] <Ankammarao> Hi mattyw
[08:33] <Ankammarao> can you help me to create terms
[08:43] <feral_> yo, do you guys know of any scalable web crawler or screen-scraper charm bundles?
[08:48] <zeestrat> viswesn: Do you perhaps have the juju/devel ppa for juju installed alongside juju/stable? You should be able to list them with: "ls -la /etc/apt/sources.list.d/"
[08:50] <zeestrat> viswesn: Is there a reason that you want the juju2.0 rc3 release? Just asking because it is an older release now. See https://launchpad.net/juju/+series
[08:51] <viswesn> zeestrat, so how can I upgrade to new version
[08:52] <viswesn> right now I am using - 2.1-beta2-xenial-amd64
[08:53] <viswesn> looking in to the launchpad.net/juju/+series I think the version which I am using it good to go ; Please correct me, if I am wrong
[08:57] <zeestrat> viswesn: The latest release in the juju/stable ppa is 2.0.1 so if you want to get on stable you'll have to make sure you only have the juju/stable ppa installed, do apt update, then downgrade or remove and reinstall juju
[09:01] <viswesn> Thanks zeestrat
[09:03] <viswesn> Zeestrat, Is I am missing something ? - http://paste.ubuntu.com/23526316/
[09:04] <viswesn> I am still seeing the same version after updating juju/stable
[09:05] <zeestrat> viswesn: Could you paste the output from "ls -la /etc/apt/sources.list.d/" and "dpkg -l | grep juju"
[09:06] <viswesn> zeestrat, http://paste.ubuntu.com/23526325/
[09:11] <viswesn> Zeestrat: http://paste.ubuntu.com/23526325/
[09:13] <feral_> can the charm command line tool list all bundles in the charm store?
[09:14] <zeestrat> viswesn: Thanks. Seems you have the juju/daily ppa in there. Try this: http://paste.ubuntu.com/23526346/
[09:16] <viswesn> Finally it is working :)
[09:16] <viswesn> Thanks a lot Zeestrat
[09:18] <zeestrat> No worries. Good luck!
[11:07] <mattyw> Ankammarao, hey there -sorry, we keep missing each other
[11:07] <mattyw> Ankammarao, you were asking about terms?
[11:13] <mattyw> Ankammarao, there's a good guide to terms here: https://jujucharms.com/docs/2.0/developer-terms. If you have any more questions I'll be around all day
[11:15] <Ankammarao> matty i have tried with charm push-term command
[11:15] <Ankammarao> but its giving error to me
[11:16] <Ankammarao> ERROR unrecognized command: charm push-terms
[11:16] <mattyw> Ankammarao, what version of charm tools do you have?
[11:16] <mattyw> Ankammarao, only charm tools 2.2 from the snap has push terms
[11:17] <Ankammarao> charm-tools 2.1.9
[11:17] <mattyw> Ankammarao, you'll need to get 2.2 from the snap store
[11:17] <Ankammarao> can you tell me how to upgrade the charm tools
[11:17] <mattyw> Ankammarao, snap install charm should do it?
[11:18] <Ankammarao> yeah i tried it and it has installed
[11:19] <mattyw> you'll need to make sure you run charm from the snap path
[11:19] <mattyw>  /snap/bin/charm I believe
[11:20] <Ankammarao> yes i tried
[11:20] <Ankammarao> charm is not a directory
[11:21] <mattyw> charm should be the binary
[11:21] <mattyw> Ankammarao, did you do snap install charm?
[11:21] <Ankammarao> yes i did
[11:23] <mattyw> Ankammarao, so /snap/bin/charm push-term -h should work?
[11:23] <Ankammarao> its working
[11:24] <Ankammarao> giving some output
[11:24] <mattyw> evilnickveitch, ping?
[11:25] <evilnickveitch> mattyw, hey
[11:27] <mattyw> evilnickveitch, so I need to improve the docs here: https://jujucharms.com/docs/2.0/developer-terms
[11:27] <mattyw> evilnickveitch, and I'd like them to be live asap - which branch of juju/docs should I submit the pr to?
[11:28] <evilnickveitch> mattyw, Hi, okay. The PR should be against master - we'll backport to relevant versions
[11:28] <evilnickveitch> thanks
[11:29] <mattyw> evilnickveitch, ok great, I'll give you a friendly ping when it's done, cheers
[11:37] <Ankammarao> mattyw, so i can use /snap/bin/charm push-term terms.txt my-group/my-terms command to create terms?
[11:38] <mattyw> Ankammarao, you can indeed
[11:41] <Ankammarao> matty, what terms.txt contains
[11:56] <mattyw> evilnickveitch, https://github.com/juju/docs/pull/1543
[11:56] <mattyw> Ankammarao, terms.txt should contain the plain text of the terms you are publishing
[11:57] <mattyw> Ankammarao, are you looking to publish a charm that requires some terms and conditions to be signed?
[11:58] <Ankammarao> i have already pushed the charm to the charm store, but i got review comments terms missing or terms not created for the charm
[11:58] <Ankammarao> so i want to create or push terms to the charm
[12:00] <mattyw> Ankammarao, are you expecting to need to create terms for the charm?
[12:00] <mattyw> Ankammarao, as the charm author that's you're decision, if you don't require terms and conditions to be signed you don't need to include them
[12:01] <Ankammarao> mattyw, when i tried to deploy the charm from the charm store it was asking for agree the terms
[12:02] <Ankammarao> mattyw so can we remove the terms if we do not require
[12:02] <mattyw> Ankammarao, which charm is this? to agree to terms you just need to run juju agree...
[12:02] <mattyw> Ankammarao, and yes - if you don't require uses to sign any terms you can just not specify any in the charm's metadata.yaml
[12:03] <Ankammarao> mattyw ,ibm-platform-ac
[12:03] <mattyw> Ankammarao, and then users won't get prompted to agree to terms when they deploy the charm
[12:03] <mattyw> Ankammarao, this charm? https://jujucharms.com/u/ibmcharmers/ibm-platform-ac/trusty/4
[12:04] <Ankammarao> mattyw,yes this only
[12:05] <mattyw> Ankammarao, so if you have any terms and conditions that users of this charm should sign they should be uploaded using charm push-term filename.text owner/termname
[12:05] <mattyw> Ankammarao, I believe there are a number of ibm terms already uploaded, but the ones needed by this charm is obviouslly an ibm decision
[12:06] <mattyw> Ankammarao, but any terms that need to be signed should be put in plain text format and put into a file which is passed as an argument to charm push-term
[12:06] <mattyw> Ankammarao, and then when the user deploys the charm and does juju agree they will be presented with the contents of this file
[12:07] <Ankammarao> mattyw, i am getting this error "error: could not read contents of "ibm-platform-ac.txt": open ibm-platform-ac.txt: permission denied" while pushing terms
[12:08] <Ankammarao> mattyw, i just pasted the content into the file .txt
[12:09] <mattyw> Ankammarao, that error would be a local problem (local to your machine) it means the command is unable to read from that file
[12:17] <Ankammarao> mattyw, thanks for help and i'll try to resolve the issue with .txt and i'll push the terms
[12:18] <mattyw> Ankammarao, no problem, sorry the docs weren't clearer, I've submitted a fix for that, if you have any more issues just let me know
[12:19] <Ankammarao> mattyw, ok np
[13:29] <capsali> hi guys
[13:31] <capsali> we have a small problem with juju2 and i hope i can get some help with it
[13:31] <capsali> we have juju2 deployed in ha with 3 state machines, MAAS as backend
[13:31] <capsali> there are 6 total models
[13:32] <capsali> the largest modle has 70 machines
[13:32] <capsali> and the smallest one has 4 machines
[13:33] <capsali> the problem is that it takes a long time for any command givent ot juju
[13:33] <capsali> on the larger model if i issue a juju status command it hangs around 40-60 second untill it displays the results
[13:34] <capsali> on the 4 machines model it is quicker, but still around 10 seconds
[13:34] <capsali> for 'juju models' the same problem, round 1min to display results
[13:34] <capsali> i have been tailing juju logs with no luck
[13:35] <capsali> there isn;t any relevant error in the logs that could trace to this problem
[13:36] <capsali> the only thing that is weird to me is that from the 3 state machines, two of them have mongodb consume around 5% of cpu and jujud around 55%
[13:36] <capsali> the first state machine mongodb stays at around 80% sometimes reaching 160-200% cpu
[13:37] <capsali> any ideas on what could be the root cause for this slowness?
[13:49] <zeestrat> Hey capsali I don't have an answer but I saw bdx having some similar load issues yesterday: https://irclogs.ubuntu.com/2016/11/23/%23juju.txt
[13:51] <zeestrat> Also, it's pretty quiet here today from juju folks due to it being a US holiday.
[14:16] <pmatulis> capsali, yeah, best open a bug
[14:27] <capsali> thanks guys
[14:27] <capsali> i would open a bug but i don't have any relevant logs to show
[14:28] <capsali> that's why i didn't open a but yet
[14:28] <capsali> and happy holiday
[14:28] <capsali> thanksgiving right?
[14:39] <viswesn> I am using logger module to write log messages to file in juju-cli-tool but I am getting logs that were specific to juju-cli-tool in the log file where as the log output from juju is shown on stdout but not in the file; how to redirect that to the log file?
[16:24] <magicaltrout>  isn't it nice when all of the USA is offline! ;)
[16:54] <mattyw> evilnickveitch, you still about?
[16:55] <evilnickveitch> mattyw, yup, I'm just working on backporting that fix
[16:56] <mattyw> evilnickveitch, you work fast - I was just about to ask what I should be doing :)
[17:12] <evilnickveitch> mattyw, should be live in stable docs in about 10 mins
[17:13] <mattyw> evilnickveitch, many thanks
[17:14] <evilnickveitch> np
[17:14] <evilnickveitch> thanks for helping
[19:36] <bdx> rick_h: happy thanksgiving
[19:37] <bdx> rick_h: hitting this pretty regularly -> http://paste.ubuntu.com/23528908/
[19:37] <bdx> rick_h: don't know if you made a bug for it the other day or not
[19:40] <bdx> can't even access my controller -> http://paste.ubuntu.com/23528918/
[19:46] <bdx> https://bugs.launchpad.net/juju/+bug/1644634
[19:46] <mup> Bug #1644634: cannot access controller <juju:New> <https://launchpad.net/bugs/1644634>