/srv/irclogs.ubuntu.com/2016/10/31/#juju-dev.txt

menn0axw: review done00:01
axwmenn0: thanks, I'll run up a 1.25 env and test on there before I land00:50
menn0axw: great, thanks00:56
menn0axw: thanks for the edits01:42
axwmenn0: so 2.4 handles the "_id $in [...]" method well - it completed instantly. using Bulk isn't terrible though, it takes 3 seconds to remove 10000 docs01:42
axwmenn0: so I'm inclined to just use Bulk for simplicity01:42
menn0axw: that SGTM01:43
axwmenn0: np01:43
axwcool01:43
menn0axw: 3s for 10000 docs locally or on azure?01:43
axwmenn0: on azure01:43
axwone last test with 2.0 on a fresh VM01:46
menn0axw: that seems like it should be fine to me01:54
axwmenn0: cool. I'm just going to test on the exact same VM size, with mongo 3.x/wiredtiger without waiting for things to go pear shaped this time. should be a better comparison01:55
axwif it's the same I'll shipit01:55
menn0axw: +101:55
wallyworldaxw: when you have time, a small one, no rush https://github.com/juju/juju/pull/651603:07
axwwallyworld: what is the "elsewhere" that tests the same functionality?03:10
wallyworldaxw: test cases in testChangeRemoteApplications03:10
axwwallyworld: LGTM03:13
wallyworldty03:13
wallyworldaxw: this line https://github.com/juju/version/blob/master/version.go#L143 causes this bug https://bugs.launchpad.net/juju/+bug/1637079 . I think we should just remove that series check entirely from ParseBinary? The bugs happens when you have a juju agent running on a system without zesty in its distro info data and the agent tries to parse zesty tools03:47
mupBug #1637079: Upgrade stuck due to out-of-date distro-info-data package <canonical-is> <eda> <juju:Triaged by alexis-bruemmer> <https://launchpad.net/bugs/1637079>03:47
axwwallyworld: SGTM, but does removing that get you all the way?03:48
wallyworldi think so, will check a bit more closely to try and be sure03:48
axwwallyworld: we should be changing the binary format to replace series with OS at some point. there's no need for separate agent binaries per series03:51
wallyworldaxw: oh tell me about it. bootstrapping on aws is sooooooo because it uploads i think 3 copies of the tools tarballs, one for each of a few series. takes forever03:54
wallyworldmaybe a 2.2 thing03:54
axwwallyworld: seriously? I thought we fixed that to just upload one, and have the controller explode it into the various series03:55
axwif we're uploading multiple times, I think we can fix that without changing the format at least03:56
wallyworldhmmm. maybe. i haven't checked in a while. maybe the tarball has grown so large it still take sages03:56
axwit does take a long time03:56
wallyworldon ADSL yeah it does :-(03:56
wallyworldaxw: two small ones for whenever https://github.com/juju/utils/pull/247 https://github.com/juju/version/pull/404:47
wallyworldaxw: thanks for reviews. there's little that can be done for other usages of GetOSFromSeries() in juju - all cases require the OS to make a decision about something wrt cloud init and such. so i'll just update the deps05:14
axwokey dokey05:15
wallyworlddamn, pulling in tip of utils breaks other apis, sigh05:23
rogpeppeanyone know ModelMachineInfo.Status is instance status or agent status?09:21
rogpeppeanyone around that may be able to do a review of a change to testing/checkers to ignore time zones when comparing times? https://github.com/juju/testing/pull/11510:13
rogpeppedimitern: ^10:14
dimiternrogpeppe: looking10:32
rogpeppedimitern: thanks!10:32
rogpeppedimitern: are you all at the sprint this week?10:33
dimiternrogpeppe: thankfully, no :)10:33
rogpeppedimitern: :)10:33
rogpeppedimitern: just it seem very quiet here atm10:33
dimiternrogpeppe: LGTM, but I'm curious - why was that needed?10:33
rogpeppedimitern: just a test failure due to two times being different only in zone (we were using UTC, bson unmarshals as local) and i got fed up. i've wanted to make this change for ages :)10:34
dimiternrogpeppe: quiet yes.. I'm tasked with making sure develop merges OK into staging though, so I haven't noticed :)10:34
=== Guest79971 is now known as ahasenack
=== ahasenack is now known as Guest85272
perrito666morning all12:07
zeestratHey, when is 2.0.1 coming to the juju/stable PPA?12:52
dimiternmgz: ping13:27
mgzdimitern: yo13:30
dimiternmgz: hey, I've been watching the last few CI runs on develop13:31
dimiternmgz: any idea about the build errors?13:31
mgzthe last few?13:31
mgzthe earlier ones were from balloons changing the packaging branch13:31
mgzbut those should be gone with the latest builds?13:32
mgzhm, something new13:32
dimiternlatest one still has a few: http://reports.vapour.ws/releases/454013:32
mgzalso those results are misleading13:33
mgzhardly anything actually ran13:33
mgzthere was talk about poking around with S3 on friday, I'll look and see what actually changed13:34
dimiternok13:34
dimiternmgz: do you think we could merge develop into staging today, or we need a bless first?13:35
mgzideally we get a bless, but of the last 10 runs most have failed due to non-juju code reasons13:35
balloonswe do need a bless. I was hoping a PR would land so we'd get a testrun -- really nothing has landed?13:36
balloonsohh, no, it landed.. I see, weird13:37
mgzstuff has landed, we're stuck on the build/publish step13:37
mgzof xenial ppc64 build at least is blocking things13:37
mgzperhaps other stuff?13:37
* mgz goes to clean up ppc64el-slave13:37
mgzwhich stilson are you today...13:38
mgzhm, 05 isn't actually out of disk13:40
mgzdimitern: I deleting a bunch of things from that machine and am trying a rerun of the ppc64 build job13:47
dimiternmgz: +113:47
mgzthat should unblock various things, obviously we have some config issues as well13:47
mgzas the jobs that failed shouldn't run before publish I presume13:47
SimonKLBwho's involved with the juju charm store development?13:54
SimonKLBi renamed a user to use it's username for a team instead, launchpad seem ok with it, but it's not possible to make the changes migrate to the juju charm store13:55
SimonKLBor at least im not sure how to do it13:55
natefinchrogpeppe: ^13:56
mgzah, standup is a different hour13:57
mgzthanks clocks...13:57
natefinchhaha13:57
natefinchI laugh, but ours changes next week13:58
mgzyeah, then standup time will move again13:58
mgzhm, no katco today?14:01
mgzshe appeareth14:02
mgzdimitern: standup!14:04
mgzalso... other people who are around?14:04
katcodimitern: macgreag1ir: voidspace: frobware: standup time14:04
voidspacekatco: oh, screw - our clocks changed and I forgot that changed standup time14:05
voidspacekatco: omw14:05
katcono worries!14:05
katcodooferlad: standup time14:06
dimiternkatco: isn't it in an hour's time?14:07
natefinchnope, you guys had daylight saving end and we haven't yet14:07
mgzdimitern: clocks, they are a changin'14:07
natefinchnext week it'll be back to the same time14:07
natefinchsince we end our saving time next week14:07
natefinchhuzzah14:07
katcodimitern: confusion abounds14:07
dimiternoh I see14:07
dimiternomw then14:07
rogpeppeSimonKLB: I'm not sure exactly what you mean by "i renamed a user to use it's username for a team instead,"14:09
=== hml_ is now known as hml
rick_h___rogpeppe: in SSO you can change the user be but that blows up on the chsrmstore without manual intervention15:11
rogpepperick_h___: yeah, we discussed it by PM15:11
rick_h___Ah cool15:12
rogpepperick_h___: my question above was because i found the grammar hard to parse15:12
SimonKLBmy bad \o15:15
SimonKLBrick_h___: would deleting the user be sufficient? because i only have some test-charms pushed15:16
SimonKLBdo whatever is the easiest for you guys15:16
voidspacedimitern: so for maas 2, "not_networks" needs to be changed in gomaasapi rather than in juju15:21
dimiternvoidspace: for maas 2.1 only IIRC - let me double check15:22
voidspacedimitern: according to bug 163919 it's maas 2.015:22
mupBug #163919: didyouknow plugin bug <Exaile:Invalid> <https://launchpad.net/bugs/163919>15:22
voidspaceuhm15:22
voidspacebug 163691915:22
mupBug #1636919: MAAS machine selected with space in violation of constraint <ci> <jujuqa> <maas-provider> <networking> <juju:Triaged> <MAAS:Invalid> <https://launchpad.net/bugs/1636919>15:23
voidspacedimitern: ah, no - it's an api change as well15:23
voidspacedimitern: (for gomaasapi)15:23
voidspacedimitern: juju needs to pass a slice of strings not a string15:23
dimiternvoidspace: according to http://maas.ubuntu.com/docs2.0/api.html#machines - not_networks is still acceptable for API 2.015:23
voidspacedimitern: I've pinged mpontillo on #juju (canonical)15:24
voidspacedimitern: no response yet, but I'll check with him15:24
voidspacedimitern: what maas API version do you see with 2.1? I don't have 2.1 setup15:25
dimiternvoidspace: I've checked the source, but as for 2.1 API docs -  http://maas.ubuntu.com/docs2.1/api.html#machines still mentions not_networks and not "not_subnets"15:26
dimiternvoidspace: I guess the docs were not updated recently15:26
voidspacedimitern: well, if they're incorrect for 2.1 they could be incorrect for 2.0 as well...15:26
mgzdimitern: I filed bugs15:26
voidspacedimitern: I'll find out15:27
voidspacemgz: the maas guys are at the sprint - as far as you know is "not_subnets" correct for 2.0 or only for 2.1?15:27
mgzfor both15:27
dimiternvoidspace: If all else fails, use the source :)15:27
voidspacedimitern: so you're saying that according to the source, "not_networks" is correct for 2.0?15:27
voidspacewe don't officially support 2.1 yet anyway ;-)15:27
mgzbug 1637009 probably what you're most interested in15:28
mupBug #1637009: [2.0,2.1] Node acquisition constraints API documentation needs to be updated to match reality <MAAS:In Progress by mpontillo> <MAAS 1.9:In Progress by mpontillo> <MAAS 2.0:In Progress by mpontillo> <https://launchpad.net/bugs/1637009>15:28
* voidspace goes to checkout maas15:28
dimiternvoidspace, yeah - I can confirm on the actual 2.0 vmaas here..15:28
voidspacedimitern: ah, so that's in contradiction to the bug that mgz just linked to15:28
mgzbug 1637182 and bug 1637192 also relevent15:28
mupBug #1637182: Help and documentation 'list of unicodes' inconsistent <MAAS:In Progress by mpontillo> <MAAS 1.9:In Progress by mpontillo> <MAAS 2.0:In Progress by mpontillo> <https://launchpad.net/bugs/1637182>15:28
mupBug #1637192: [2.0,2.1] Allocate using subnets or not_subnets with space fails <MAAS:Triaged by mpontillo> <MAAS 1.9:Triaged by mpontillo> <MAAS 2.0:Triaged by mpontillo> <https://launchpad.net/bugs/1637192>15:28
mgzand bug 163625015:30
mupBug #1636250: [2.1] machines allocate API returns a random machine if incorrect - parameters are used <MAAS:Fix Committed by andreserl> <https://launchpad.net/bugs/1636250>15:30
mgznot_networks is accepted and silently ignored on 2.0 and 2.115:31
dimiternmgz: not quite: http://paste.ubuntu.com/23407376/15:31
dimiternmgz: for 2.1 - http://paste.ubuntu.com/23407383/15:33
dimiternbut I'll test it with the MAAS CLI manually on both15:33
mgzwhat am I looking for there dimitern?15:33
mgzI only see (wrong) docstring matches for your grep15:34
mgzalso, bugs document the pretty extensive testing I did for this across three maas versions15:35
dimiternmgz: I've tried `$ maas 21-root machines allocate dry_run=True not_subnets=space:0 verbose=True` on 2.1 and got `unorderable types: Subnet() < Subnet()`15:37
dimiternwith not_networks there's no error, but it doesn't seem to work15:38
mgzdimitern: see bug 1637192 as linked above15:38
mupBug #1637192: [2.0,2.1] Allocate using subnets or not_subnets with space fails <MAAS:Triaged by mpontillo> <MAAS 1.9:Triaged by mpontillo> <MAAS 2.0:Triaged by mpontillo> <https://launchpad.net/bugs/1637192>15:38
mgzthere's a bit more background to that that's on a maas mailing list15:39
mgzbut I think the bug has the conclusion at least15:39
mpontillodimitern: the 'unorderable types' one is a bug in the error message. what we're trying to do is render a string that says something like "failed to match constraint: xyz", but when we go to figure out what to put in xyz we crash ;-)16:33
mpontillodimitern: https://code.launchpad.net/~mpontillo/maas/update-constraints-docs--bugs-1637182-1637009/+merge/309617 clarifies the docs16:34
dimiternmpontillo: cheeers! :)16:34
mpontillodimitern: but yeah, I can confirm that going from 1.x to 2.x we renamed the '[not_]networks' constraint to '[not_]subnets'. MAAS 2.1 was also recently changed to reject unknown constraints.16:39
dimiternmpontillo: so *both* 2.0 and 2.1 API only accept "not_subnets" (even if it doesn't complain in the former case) ?16:40
mpontillodimitern: correct, when we moved to MAAS 2.x we made that change. we also dropped legacy 'connected_to' and 'not_connected_to' constraints in 2.x16:41
dimiternmpontillo: ok, thanks for confirming!16:44
mpontillodimitern: voidspace: np. also, be aware when testing this that the corresponding *positive* constraints will probably not do what you expect. that is, 'subnets' and 'not_subnets' do not filter an inverse set of machines if multiple subnets match the specifier.16:45
mpontillo(long story short, only matching nodes *not* in a set of subnets is well-supported, if you try to pass in, for example, subnets:space:x and space x has 3 subnets, we'll try to find a node with all 3, which is probably not useful)16:46
mpontillobut that is more of a wishlist because this works as-expected when using the interfaces constraint.16:47
voidspacempontillo: ok, thanks16:49
=== Guest85272 is now known as ahasenack
=== ahasenack is now known as Guest84237
redirrick_h___: yt?18:27
perrito666voidspace: still working?18:54
voidspaceperrito666: still around anyway18:54
perrito666voidspace: I am trying to determine an issue that is most likely unrelated to this but am getting a constant spam error because juju cant  SetLinkLayerDevices18:55
perrito666voidspace: how big of an issue is that error?18:55
voidspaceperrito666: ah, I've seen that - I think it's spurious18:55
perrito666voidspace: apparently Its trying to use the same id for more than one thing18:55
perrito666voidspace: ack, I thought so18:56
voidspaceperrito666: dimitern is really the one who needs to answer I'm afraid18:56
perrito666yep, blame said the same but he is not here :p18:56
voidspaceperrito666: but I saw the same error when I was trying to diagnose a vsphere issue - and it had nothing to do with that error18:56
perrito666voidspace: yeah, same here18:56
perrito666:)18:56
perrito666spaces are blowing all over the place in vsphere18:57
voidspaceperrito666: yeah, that needs fixing - it shouldn't error out if spaces aren't supported18:58
voidspaceperrito666: if you file a bug I'll fix it ;-)18:59
perrito666voidspace: I dont have enough information, I believe this is actually causing a problem for me here19:02
natefinchperrito666: what auth types does vsphere allow?20:04
natefinchperrito666: just userpass?20:05
natefinchanyone else know?  Would be nice if our docs specified this :/20:06
natefinchlooks like just userpass from the credential s chema20:07
voidspacenatefinch: perrito666: I've only ever *seen* userpass...20:11
voidspaceperrito666: actually, the specific issue I saw was "unrecognised type" for an interface, not id re-use20:11
voidspaceperrito666: so that is "new"20:11
babbageclunkmorning everyone! I'm in Hamilton!20:23
perrito666natefinch: I have the same experience as voidspace20:27
perrito666voidspace: I learned it was due to id reuse after digging into the code the error is completely misleading20:27
redirbabbageclunk: congrats20:35
veebersbabbageclunk: nice! Where is your final destination in NZ?20:35
voidspaceperrito666: ah, ok20:37
babbageclunkveebers: uh, a grave somewhere I guess? ;)20:39
babbageclunkI mean, Welly.20:39
babbageclunkBut we'll have a longish boringish interlude in Palmerston North while all our stuff is being shipped.20:40
veebersbabbageclunk: wow dark. I love it20:44
babbageclunkveebers: I mean, Palmy's not that bad.20:44
veebers^_^20:44
perrito666hey all, how do I pass availability zone to bootstrap?21:12
mupBug #1637695 changed: Charm-guide: Openstack on LXD directions do not work <juju:New> <https://launchpad.net/bugs/1637695>22:04
perrito666Alexis wallyworld I'll be a few mins late to the standup sorry23:13
wallyworldnp23:13

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!