=== _thumper_ is now known as thumper
thumperwallyworld, axw: if we are bumping all the API versions and hacking at the wire protocol with a machette, can you please add explicit serialization directives to everything on the wire?00:22
wallyworldwe can try00:22
thumpersurely this is just a sed script right?00:22
=== JoseeAntonioR is now known as jose
thumperbecause sed is all you need00:22
* wallyworld growls at thumper 00:23
* thumper hums the "all you need is love" tune...00:23
thumperall you need is sed... sed...00:23
thumpersed is all you need00:23
* thumper is distracting himself from what he really needs to be doing00:24
mupBug #1540076 changed: Storage Hooks before Install <juju-core:Invalid> <https://launchpad.net/bugs/1540076>00:26
* thumper is wondering when master will get another CI run...00:32
thumperlast was several days ago...00:32
thumperlike four00:32
thumperthe dep engine merge hasn't been blessed or cursed yet...00:32
wallyworldthumper: CI is paused over the weekend, should get another run later tonight our time. i'm keen to see it get a run because after i merged the dep endgine stuff into the api-command-rename feature branch CI reports intermittent leadership failures which i claim have nothing to do with renaming some methods00:49
axwwallyworld: was out, Charlotte's first day of grade one. responded to your email01:16
wallyworldnp, hope she went ok01:16
axwwallyworld: I think one use-case for adding volumes after deploy is, e.g. if you have a MAAS and add a disk to the machine01:39
axwwallyworld: MAAS has no agent, so you have no other way of discovering it01:39
wallyworldthat is true, but that then becomes an add storage thing maybe01:40
wallyworldneeds thought as to how it all fits the model01:40
axwwallyworld: how do you mean? add-storage would always be required, to associate the volume with a unit01:41
wallyworldexactly, that's after a unit is deployed, you add a volume, possibly one you added post deploy to the machine01:42
wallyworldbut at deploy time, i'm not sure it makes sense to have to have storage and placement directives macthing01:42
wallyworldmaybe i'm wrong01:42
axwwallyworld: well if you have the machine already, then you wouldn't be able to deploy a unit that *requires* storage if you only have that OOB-added disk on the machine01:43
axwwallyworld: anyway, this is just speculation, needs more requirements01:44
wallyworldthumper: can you let me know if you have 5 minutes for a chat/question01:51
thumperwallyworld: sure, now is as good as any01:51
wallyworldok, 1:101:51
davecheneythumper: it works!03:48
davecheneyroot@ip-10-251-40-215:~# echo -e "GET /debug/pprof/goroutine?debug=1 HTTP/1.0\r\n" | socat unix-connect:/tmp/.5636.pprof STDIO | pastebinit03:48
* thumper took a minute disecting that command03:49
thumpervery cool03:49
davecheneyyeah, it's a mouthful03:50
thumperdavecheney: what are the lines like this: 2 @ 0x437b2a 0x446382 0x445372 0x713277 0x737040 0x464d4103:50
davecheneymost http tools are like "unix socket, wat?!"03:50
davecheneythose are the raw program counters03:50
thumperis there memory dumps?03:51
davecheneyhere is what the comp[uter see, http://paste.ubuntu.com/14847399/03:51
davecheneythe extra lines are for humans, see the ?debug=1 flag03:51
thumpermuch nicer to see the full method03:51
thumperwhat about memory?03:52
thumpercan we see that?03:52
davecheneyi don't immediately know how to interpret those numbers03:54
davecheneybut pprof can03:55
davecheneyi've never found the go heap profiler to tell me useful information03:55
davecheneyi wanted to implement this facility so I could find out what the goroutines were doing inside a program03:55
davecheneyfriday the juju deployer worked fine for me04:34
davecheneytoday, nothing04:34
thumpersee y'all tomorrow05:06
jogdavecheney, juju-deployer==0.3.6 is an old version of deployer. You probably want 0.6.1-1 from 'deb http://ppa.launchpad.net/juju/stable/ubuntu trusty main'05:07
=== mup_ is now known as mup
mupBug #1540047 changed: Error in Jujuclient with Python3 <python-jujuclient:Fix Released by aisrael> <https://launchpad.net/bugs/1540047>06:54
mupBug #1540047 opened: Error in Jujuclient with Python3 <python-jujuclient:Fix Released by aisrael> <https://launchpad.net/bugs/1540047>07:00
mupBug #1540047 changed: Error in Jujuclient with Python3 <python-jujuclient:Fix Released by aisrael> <https://launchpad.net/bugs/1540047>07:09
frobwarejam: ho? (though I have no camera today.)09:03
jambe there in just a sec09:03
dimiternvoidspace, frobware, fwereade__, standup?10:02
voidspacedimitern: omw10:02
voidspacedimitern: got booted out - rejoining10:03
dooferlad_voidspace: are you rejoining?10:20
=== dooferlad_ is now known as dooferlad
dooferladok, 2fa for me.10:21
dooferladyay, in the middle of a hangout!10:21
voidspacedimitern: jam: dooferlad: not sure if any of my last messages got through10:26
voidspacedimitern: jam: dooferlad: internet went down briefly10:26
voidspacedimitern: jam: dooferlad: dependency engine stuff may mean I get to simplify my tests a bit, I think that was all I wanted to say10:27
dooferladvoidspace: we didn't get that bit. sounds goodf.10:27
wallyworldfwereade__: hey, did you have 5 minutes, i just wanted to run something by you10:27
dimiternvoidspace, that sounds like a good next step, yeah10:29
mupBug #1540301 opened: adding storage to a unit should be able to take a specified block device <storage> <juju-core:Triaged> <https://launchpad.net/bugs/1540301>11:07
mupBug #1540316 opened: provider/maas: bridgescript should support vlans <maas-provider> <juju-core:New> <https://launchpad.net/bugs/1540316>11:40
axwwallyworld: might be a minute or two late11:58
davecheneyjog: i'm running the version of hte juju-deplouyer that ships in trusty11:59
davecheneyand it worked right up til friday12:00
davecheneybut this week it just decided not to work12:00
wallyworldperrito666: meeting?12:02
cheryljfwereade__: ping?12:37
=== akhavr1 is now known as akhavr
mattywwwitzel3, you around mate?13:53
mattywcherylj, don't suppose you know anyone who might be awake and knows about the lxd provider, I'm having problems13:54
=== akhavr1 is now known as akhavr
wwitzel3mattyw: ping14:08
mattywwwitzel3, hey hey, you worked on the lxd provider?14:08
wwitzel3mattyw: yep, ericsnow and myself14:08
mattywwwitzel3, awesome, I'm having problems with it (it was working fine) I've almost finished typing it all out in an email I was going to put on juju-dev email list. If it's ok I'll finish that and ping when it's sent. I basically need help debugging and env that seems screwed14:09
mattywwwitzel3, I'll finish off the email to save time typing it all out again14:09
wwitzel3mattyw: yeah, ok, I'm not on the list anymore, so if you want to also pastebin it to me, I'll give it a read and see if I have any insight14:10
mattywwwitzel3, I've emailed you as well14:12
wwitzel3that works14:12
tasdomasmenno, ping?14:16
wwitzel3mattyw: I'd also ping ericsnow and direct him to the list message, he might have some insight on it too .. but yeah, I'll poke it a bit more and see if anything shakes out14:23
mattywericsnow, are you around?14:23
mattywI wish irc displayed timezones for everyone14:23
wwitzel3mattyw: he'll be around soon (if he isn't out of office)14:25
wwitzel3mattyw: moonstone standup is in 30 minutes14:25
frobwaremgz, did we ever get a dedicated 1.25 CI run for bug 1532167  - this was the backport of the maas-spaces bridge script14:31
mupBug #1532167: maas bridge script handles VLAN NICs incorrectly <addressability> <maas-provider> <network> <juju-core:Triaged> <juju-core 1.25:In Progress by frobware> <https://launchpad.net/bugs/1532167>14:31
mupBug #1540394 opened: Juju does not handle 429 "too many requests" from Azure <azure-provider> <bootstrap> <ci> <juju-core:Triaged> <https://launchpad.net/bugs/1540394>14:46
mupBug #1540394 changed: Juju does not handle 429 "too many requests" from Azure <azure-provider> <bootstrap> <ci> <juju-core:Triaged> <https://launchpad.net/bugs/1540394>14:52
mupBug #1540394 opened: Juju does not handle 429 "too many requests" from Azure <azure-provider> <bootstrap> <ci> <juju-core:Triaged> <https://launchpad.net/bugs/1540394>14:55
ericsnowmattyw: present, but about to go to standup14:58
ericsnowmattyw: I'll ping you when we're done14:58
mattywericsnow, ok cool14:58
ericsnowmattyw: nevermind, I'm the only one around apparently14:59
mattywericsnow, take a look at my email to juju-dev for the strarting point15:01
ericsnowmattyw: will do15:01
katco`sinzui: ping15:28
katco`or, mgz: ping15:29
sinzuihi katco`15:29
katco`sinzui: o/15:29
katco`sinzui: at the charmer summit, have a person here trying to try out juju on joyent15:30
katco`sinzui: and he's getting a strange error on bootstrap15:30
katco`sinzui: (one sec getting err)15:30
sinzuikatco`: joyent has several ill regions over the last few weeks. us-east-3 is good. us-east-2 is locked down. us-east-1 has network issues, us-west-1 is not cleaning up networks15:31
katco`sinzui: we're using eu regions15:31
katco`sinzui: 2016-02-01 15:27:04 ERROR juju.cmd supercommand.go:429 there was an issue examining the environment: cannot create credentials: An error occurred while parsing the key: asn1: structure error: tags don't match (16 vs {class:0 tag:23 length:23 isCompound:true}) {optional:false explicit:false application:false defaultValue:<nil> tag:<nil> stringType:0 timeType:0 set:false omitEmpty:false} pkcs1PrivateKey @215:31
katco`sinzui: the environments.yaml looks like it could be ok, but wouldn't completely rule that out15:32
sinzuikatco`: I don't think someone setup their account keys properly. CI has never seen that kind of issue15:32
katco`sinzui: so we checked the keys in his account, and they match what's in environments.yaml15:33
katco`sinzui: i've not used joyent. what kind of setup could be wrong in this case?15:33
sinzuikatco`:  I've never seen an error like that to day15:34
katco`sinzui: hm ok15:34
katco`sinzui: manta information should be the same as sdc?15:36
sinzuikatco`: my config looks like this https://pastebin.canonical.com/148857/15:36
katco`sinzui: ahhh possibly what's wrong. the key he posted looks possibly like a fingerprint15:37
sinzuikatco`: yes, sdc-key-id and anta-key-id are the same, as ar sdc-user and manta-user.15:37
katco`sinzui: scratch that, he's specifying the path to the key15:38
sinzuikatco`: private-key-path works, though I don't use it often15:39
katco`sinzui: he's on os x if that helps15:39
sinzuikatco`: I haven't seen a difference between OS X and Ubuntu for joyent. ssh and keys are the same.15:40
katco`sinzui: hm ok15:40
sinzuikatco`: unless someone trued to compile their own juju on that host. OSX requires CGO=1 to link to the native keystore15:41
katco`sinzui: nah he just brew installed15:41
katco`sinzui: fyi when he tried to brew install alpha1, he got an error15:42
sinzuikatco`: we don't support it15:42
katco`sinzui: looked like the brew recipe had some kind of utf error15:42
katco`sinzui: ah ok15:42
sinzuikatco we onlt support jujus in *releaed* streams. other wise peoples configs break when they get updates15:43
katco`sinzui: right, we're just showing alpha1 here to show everyone the new stuff15:43
katco`sinzui: but seems like a bug in the brew recipe for 2.0? or are you saying we don't do the support for brew?15:43
sinzuikatco`: not a bug is the recipe, it is about streams not working at the time the binaries are meade15:44
katco`sinzui: no, i'm saying the recipe seems broke. as in brew install doesn't work for alpha115:45
sinzuikatco`: we did suport devel, users were not happy about incompatible configs15:46
sinzuikatco`: We solved this by creating cient for testers https://launchpad.net/juju-core/+milestone/2.0-alpha1 got clients *before* ubuntu users15:46
katco`sinzui: right, that's what he ended up downloading15:47
mupBug #1540437 opened: lxd provider: machines stuck at "pending" <juju-core:New> <https://launchpad.net/bugs/1540437>16:04
mupBug #1540447 opened: error: r.runner.RunCommands: tomb: dying <run> <juju-core:Incomplete> <juju-core 1.25:Triaged> <juju-core api-command-rename:Invalid> <https://launchpad.net/bugs/1540447>16:04
mupBug #1540437 changed: lxd provider: machines stuck at "pending" <juju-core:New> <https://launchpad.net/bugs/1540437>16:07
mupBug #1540447 changed: error: r.runner.RunCommands: tomb: dying <run> <juju-core:Incomplete> <juju-core 1.25:Triaged> <juju-core api-command-rename:Invalid> <https://launchpad.net/bugs/1540447>16:07
mupBug #1540437 opened: lxd provider: machines stuck at "pending" <juju-core:New> <https://launchpad.net/bugs/1540437>16:10
mupBug #1540447 opened: error: r.runner.RunCommands: tomb: dying <run> <juju-core:Incomplete> <juju-core 1.25:Triaged> <juju-core api-command-rename:Invalid> <https://launchpad.net/bugs/1540447>16:10
voidspacedimitern: omw16:18
natefinchmorning ericsnow16:33
ericsnownatefinch: hey16:33
ericsnownatefinch: interested in a late standup?16:33
natefinchericsnow: yeah, definitely16:33
frobwarecherylj, some success with VLAN nics on 1.25 - https://bugs.launchpad.net/juju-core/+bug/1532167/comments/2816:37
mupBug #1532167: maas bridge script handles VLAN NICs incorrectly <addressability> <maas-provider> <network> <juju-core:In Progress by frobware> <juju-core 1.25:In Progress by frobware> <https://launchpad.net/bugs/1532167>16:38
frobwarecherylj, this change was also going to get a CI branch as well. I haven't seen any reports. The PR is good to go, just waiting on sanity CI run.16:38
voidspacedimitern: frobware: do we still have the networking thing this afternoon?16:39
frobwarevoidspace, yes.16:39
voidspacefrobware: thanks16:39
cheryljfrobware: okay, I had held off since the initial feedback showed it had problems.  I'll get it on the queue16:40
frobwarecherylj, thanks.16:41
dimiternvoidspace, we do, but I might skip it16:41
mupBug #1540469 opened: [ARM64][LXD Provider][2.0-alpha1-0ubuntu1~16.04.1~juju1] juju run command ERROR fork/exec /usr/bin/ssh: cannot allocate memory <juju-core:New> <https://launchpad.net/bugs/1540469>16:46
voidspacedimitern: ok16:47
voidspacedimitern: frobware: dooferlad: unless anyone has any questions/follow up for Jay, maybe we should skip it this week?16:48
dimiternvoidspace, +1 from me16:48
frobwarevoidspace, dimitern, dooferlad: agreed. need to merge :)16:50
voidspaceI've emailed16:50
dimiterncheers voidspace17:00
voidspacedimitern: can I tell the difference, on a buffered channel as I *do not* want to block, between a closed channel and a channel with no messages available17:01
voidspacedimitern: I'm starting to think that the bool is just easier17:01
voidspacedimitern: I think I can17:03
voidspacedimitern: unping17:03
natefinchvoidspace: a closed channel never blocks17:03
natefinchvoidspace: an empty channel always blocks17:03
voidspacenatefinch: and I need to tell the difference between those two cases17:04
voidspacenatefinch: but I think I can use the ok parameter for that17:04
voidspacenatefinch: ah, I misread17:04
voidspacenatefinch: I want a non-blocking way to tell if a channel is closed or not17:04
voidspacenatefinch: just reading from it isn't enough as it will block if not closed17:05
voidspacenatefinch: but I can provide a default path in the select for that case17:05
natefinchvoidspace: yeah, was goign to say, with a default you get the non-blocking, as long as you're ok with actually taking a value off the channel if there's something there17:08
natefinchvoidspace: also, for a := range ch {    works really nicely if you're looping anyway17:08
voidspacenatefinch: thanks17:09
voidspacenatefinch: in my case I'm not reading from the channel, just need to know if it's closed17:10
natefinchvoidspace: You can't tell if it's closed without trying to read from it.. the notification that it's closed is a value you read off the channel.... Why do you need to know if a channel is closed without reading off it?17:12
voidspacenatefinch: I thought it was a common pattern to use a channel to signal something - the signal being that you close the channel17:14
voidspacenatefinch: reading from the closed channel then doesn't block - which is how you know it's closed17:14
natefinchvoidspace: yes17:14
voidspacenatefinch: the problem was that attempting a read would block, and I need the check to be non-blocking17:15
voidspacenatefinch: but that's easy enough with a default path in the select17:15
voidspacenatefinch: so no problem :-)17:15
natefinchvoidspace: yep17:15
dimiternvoidspace, dooferlad, frobware, here it is: http://reviews.vapour.ws/r/3693/17:25
voidspacedimitern: cool, mine is nearly ready for review too17:25
dimiternin the mean time I'm still finishing a few tests17:26
voidspacedimitern: dooferlad: frobware: http://reviews.vapour.ws/r/3694/17:34
voidspacedimitern: looking at your review17:34
dimiternvoidspace, ta, looking at yours17:35
voidspacedimitern: switching to a channel meant undoing a bunch of code, but it is nicer17:35
dimiternvoidspace, I suspected as much ;)17:37
frobwaredimitern, taking a look now; would some manual testing help at all?17:42
dimiternfrobware, sure, in fact what I'm seeing now is that it seems to work live (bindings included), but I still have hard time fixing the unit tests17:44
frobwaredimitern, how many unit tests are broken? what's the nature of the breakage? and depending on how many are to be addressed could these be done post the merge as collateral damage?17:45
dimiternfrobware, so the biggest issue is one of the apiaddressupdater tests hang17:45
dimiternfrobware, the rest are mostly trivial - e.g. endpoint_bindings_test.go, service_test.go - related to incomplete test setup or outdated asserts to fix17:46
frobwaredimitern, for the test that hangs is this something the CI test would run into?17:47
dimiternfrobware, well, yeah - the merge bot will hang17:47
dimiternfrobware, I'm close to actually skipping that test for now17:48
frobwaredimitern, right. :)17:48
frobwaredimitern, ok, another way. if we skip the test, is there likely to be a genuine functional failure that CI would run into.17:48
dimiternfrobware, I don't believe so17:53
frobwaredimitern, so we could throw caution to the wind here.17:54
frobwaredimitern, cherylj: another way is to get a CI run on your branch before we merge to maas-spaces17:54
dimiternfrobware, the test in question is related to the legacy address selection by scope followed by filtering of lxcbr0 addresses, both of which are skipped on 1.9 with controller space used for selection instead17:55
frobwaredimitern, as an aside just found an interesting problem with lxcbr017:55
dimiternfrobware, that's perfect, if it can be arranged17:55
frobwarecherylj, ^^17:55
frobwaredimitern, is your branch now rebased against maas-spacs? I know on friday you were holding off17:56
dimiternfrobware, I rebased before proposing, that's why it took some time - a couple of conflicts - easy to resolve though17:57
voidspacedimitern: frobware: manual test on my branch works fine by the way17:57
dimiternvoidspace, I'm still looking, but it will take some time as I have a few suggestions17:58
* cherylj reads scrollback18:01
voidspacedimitern: ok18:01
natefinchericsnow: so, for deploy --resources, if we're doing multiple resources as a single string, space separated, how do we handle paths with spaces in them?  like --resources "foo=./bar foo2=./my docs/baz"?18:03
natefinchrick_h__: ^^18:04
ericsnownatefinch: --resources foo="./bar" foo2="./my docs/baz"18:05
ericsnownatefinch: or  --resources "foo=./bar" "foo2=./my docs/baz"18:05
ericsnownatefinch: or  --resources foo=./bar "foo2=./my docs/baz"18:06
voidspacedimitern: are you passing controller space straight through to maas as a constraint at bootstrap time18:06
ericsnownatefinch: any of those should work18:06
natefinchericsnow: that's different than how constraints work, though18:08
rick_h__natefinch: understand, it'll have to be in order to be cross platform/etc. None of the others have actual directories in there like that.18:09
ericsnownatefinch: if this is not a problem that constraints has then we'll probably have to do it differently than constraints, no?18:09
rick_h__natefinch: constraints are built by us so we got to curate what was in there. I'd be curious if you can create a space or storage pool with a space in the name?18:09
rick_h__guessing not18:09
natefinchericsnow, rick_h__ : it's also sorta hard to parse.... juju deploy mysql --resources foo=bar mydatabase  is mydatabase the name of the service or a resource?18:10
ericsnownatefinch: you'd have to use quotation marks18:10
dimiternvoidspace, not exactly - it's a bootstrap argument which if unset will be inferred and set during bootstrap (see the finalizerWrapper)18:11
natefinchericsnow: no, that could be legal for deploying mysql with the servicename mydatabase18:11
natefinchericsnow: or it could be a typo for a resource called mydatabase without a path18:12
natefinchmy point is --flag item1 item2 item3   is really hard to parse unless you guarantee it has to be the last thing on the line18:13
natefinchwhich is probably why constraints have to be a single string18:13
natefinchericsnow: looks like gnuflag doesn't even support that kind of thing18:15
ericsnownatefinch: so we use a comma for a separator?18:16
natefinchericsnow: that or semicolon.... I think we use semicolon somewhere else....18:16
natefinch(although now I can't find where... maybe I'm crazy)18:18
natefinchericsnow: oh, well, loggo uses semicolons *shrug*18:19
voidspacedimitern: right, but is it used to select the space to bootstrap *to*?18:24
voidspacedimitern: (as well)18:24
frobwarecherylj, ping18:25
dimiternvoidspace, no, that's what bootstrap constraints are for18:25
cheryljfrobware: in mtg, give me a few18:26
frobwarecherylj, ack18:26
voidspacedimitern: so you could set controller-space and end up with an apiserver not in the controller space?18:26
dimiternvoidspace, and in fact if you specify --controller-space admin-api, you'll get a node there, as after validating the controller space we also update the bootstrap constraints to match18:26
voidspacedimitern: ok, so the controller-space *is* turned into a bootstrap constraint?18:27
voidspacedimitern: (that's what I was really asking - but I can't see the code that does that)18:27
voidspacedimitern: because if so we have an issue with the space name18:27
dimiternvoidspace, but if you don't specify --controller-space, you'll get arbitrary node, from which we'll then infer contr.space and also set env. constraints18:27
voidspacedimitern: I am specifically asking about the case where you *do* specify it18:28
dimiternvoidspace, yeah, the issue is commented in a todo18:28
voidspacedimitern: we'll have an issue with space names18:28
dimiternvoidspace, that we need to apply the same transformation as in discoverspaces18:28
voidspacedimitern: the bootstrap contraint should be a maas space name, but we require controller space to be a juju space name18:28
voidspacedimitern: right18:28
voidspacedimitern: that's the point I wanted to make18:28
dimiternvoidspace, well, both need to be a valid juju space name18:28
voidspacedimitern: but it's still a todo then?18:28
voidspacedimitern: except you can't "untranslate"18:29
voidspacedimitern: our name transformation is one way only18:29
voidspacedimitern: you can't go from juju name back to maas name18:29
dimiternvoidspace, so you can't use "space=Default space" in cons or --controller-space "Default space" as well18:29
voidspacedimitern: we'll have to do discovery on the client I'm afraid and then match the name18:29
dimiternvoidspace, you can :) that's why we discover them and keep both id and name18:29
voidspacedimitern: and for the bootstrap constraint the user will have to "guess" what the juju name will be18:30
voidspacedimitern: not before discovery has been done you can't18:30
dimiternvoidspace, there are still things to fix, I'll give you that :)18:30
voidspacedimitern: and discovery hasn't been done until after machine-0 has been selected and jujud is runnign18:30
dimiternvoidspace, but it's a necessary first step18:30
dimiternanyway, really should be going now, perhaps back later18:31
voidspacedimitern: why don't we just use provider names in state instead of having restricted juju names requiring a transformation?18:31
voidspacebecause of binding syntax restrictions I suppose :-(18:31
dimiternand because we have provider ids on maas only - i.e. not the common ground18:31
voidspacedimitern: maas is the only place where we need discovery18:32
voidspacedimitern: so technically it is fully common ground...18:32
dimiternvoidspace, I'll think about it tomorrow and I'm happy to listen to ideas how to generalize this approach18:32
voidspacebut anyway, this is just a distraction18:32
voidspacelife would be easier if we dropped the name restrictions and didn't have to do the transformation though18:33
voidspace(well - easier in places, maybe harder in others)18:33
dimiternyeah - mongo special chars in keys, and bad cli ux for constraints and bindings..18:33
dimiternthere's a better way I'm sure18:34
katco`sinzui: hey, got past the problem. getting a new error "cannot read product data, invalid URL "https://us-east.manta.jpyemt.com/cpcjoyentsupport/public/juju-dist/tools/streams/v1/com.ubuntu.juju:devel:tools.json""18:35
katco`sinzui: what environments.yaml thing do i tweak to make that work?18:35
katco`sinzui: again he's using 2.0-alpha118:36
sinzuikatco`: per the annoucenment to the juju and juju-devel lists, users of 2.0-alpha1 in aws, joyent, and azure must set "agent-metadata-url: https://streams.canonical.com/juju/tools" which restore 1.x behaviour18:37
katco`sinzui: ty trying now18:40
katco`sinzui: sorry for the verbose questions, in a bar trying to get this to work lol18:40
sinzuikatco`: :) that situation is crazy. by manually setting the streams to the default location that juju is already checking, it will find the agents in the public cloud it said it could not find.18:41
katco`sinzui: ty! that seems to be working18:45
perrito666cherylj: will get coffee, might be a couple of mins late depending on the expreso machine mood18:52
cheryljperrito666: np :)18:52
perrito666back, its so hot outside that the machine didnt need to pre-heat18:57
=== jog_ is now known as jog
frobwarecherylj, just wanted to say that dimiter has committed changes to his dev branch only. the tests that he mentioned in the meeting still need fixing but are simply commented out and skipped for now. Is it possible to get a CI run on his branch so we can look at the net result in the morning?19:33
frobwarecherylj, PR -> https://github.com/juju/juju/pull/425519:34
mupBug #1540469 changed: [ARM64][LXD Provider][2.0-alpha1-0ubuntu1~16.04.1~juju1] juju run command ERROR fork/exec /usr/bin/ssh: cannot allocate memory <juju-core:Invalid> <https://launchpad.net/bugs/1540469>19:59
mupBug #1540469 opened: [ARM64][LXD Provider][2.0-alpha1-0ubuntu1~16.04.1~juju1] juju run command ERROR fork/exec /usr/bin/ssh: cannot allocate memory <juju-core:Invalid> <https://launchpad.net/bugs/1540469>20:05
=== akhavr1 is now known as akhavr
natefinchanyone online who knows how deploying bundles works with the juju client?20:07
perrito666natefinch: dont you need deployer for bundles?20:07
natefinchperrito666: it's been added to the client20:07
mupBug #1540469 changed: [ARM64][LXD Provider][2.0-alpha1-0ubuntu1~16.04.1~juju1] juju run command ERROR fork/exec /usr/bin/ssh: cannot allocate memory <juju-core:Invalid> <https://launchpad.net/bugs/1540469>20:08
natefinchit looks like we just blindly throw away all CLI flags if you target a bundle20:09
* perrito666 is suddenly attacked in linkedin by solo recruiters offering the dream job, I wonder what is the algo that triggers those20:10
lazypower|summitnatefinch - are you referring to the new "juju deploy" or python juju client?20:20
thumpercherylj: did you want to talk through those few bugs?20:22
thumpero/ lazypower|summit20:23
lazypower|summit\o heyo thumper20:23
cheryljthumper: give me a minute, I'm chatting with frobware20:24
thumpermramm: are we chatting today?20:24
natefinchlazypower|summit: juju deploy20:24
lazypower|summitnatefinch - interesting, what flags were you passing that weren't respected? i can try to reproduce over here to confirm if you'd like20:25
natefinchlazypower|summit: I haven't actually tried it, was just looking at the code20:25
rick_h__thumper: he's in DE still and might be be around. after 9pm atm20:25
lazypower|summitrick_h__ - while i see that you're here - code challenge one. We still cool to riff on slides tomorrow am?20:26
rick_h__lazypower|summit: definitely20:26
lazypower|summit<3 awesome. 'preciate you20:26
natefinchlazypower|summit: basically any deploy flag at all, other than storage, looks like we just drop on the floor... which, granted, most of them don't make sense when deploying a bundle... like series or numunits or spaces... it's just surprising that I don't see code to alert the user that they've typed a command that doesn't make any sense20:28
* perrito666 discovers that the dual channel setup on his computer was the exact oposite than what is on the mobo manual...20:28
lazypower|summitnatefinch - yeah, i can see that being obtuse... Messaging would be good there.20:29
* lazypower|summit hattips20:29
lazypower|summiti'm outy 5k for now, see yinz tomorrow20:29
perrito666natefinch: it would be nice to yell one time per flag that doesnt make sense20:30
perrito666so we avoid the typicall loop that users have to endure on some apps to figure out all that is wrong20:30
natefinchperrito666: yeah, definitely.  but right now it won't yell at all, it just silently ignores the flags and deploys the bundle, which is far worse20:30
perrito666natefinch: sounds like you just bought yourself a bug report and a task? :p20:31
thumperlazypower|summit: how goes the summit?20:32
mupBug #1540469 opened: [ARM64][LXD Provider][2.0-alpha1-0ubuntu1~16.04.1~juju1] juju run command ERROR fork/exec /usr/bin/ssh: cannot allocate memory <juju-core:New> <https://launchpad.net/bugs/1540469>20:35
cheryljthumper: you still free?20:36
thumpercherylj: briefly20:36
cheryljthumper: standup HO?20:37
mupBug #1540580 opened: Broken symlink to charm breaks `juju deploy` <juju-core:New> <https://launchpad.net/bugs/1540580>20:47
mupBug #1540580 changed: Broken symlink to charm breaks `juju deploy` <juju-core:New> <https://launchpad.net/bugs/1540580>20:50
mupBug #1540580 opened: Broken symlink to charm breaks `juju deploy` <juju-core:New> <https://launchpad.net/bugs/1540580>20:53
frobwarecherylj, before I go... there will be no blessed build if the CI tests still exercise against MAAS 1.7 and 1.8. Just a heads-up.20:57
cheryljfrobware: yes, thank you :)20:58
natefinchericsnow: meeting?21:33
cheryljthumper: looks like master got a bless, so you can merge it22:04
mupBug #1540647 opened: local provider: Name com.ubuntu.Upstart does not exist <kanban-cross-team> <landscape> <juju-core:New> <https://launchpad.net/bugs/1540647>22:08
mupBug #1540647 changed: local provider: Name com.ubuntu.Upstart does not exist <kanban-cross-team> <landscape> <juju-core:Invalid> <https://launchpad.net/bugs/1540647>22:41
mupBug #1540650 opened: lxd provider: juju destroy-controller hangs <juju-core:New> <https://launchpad.net/bugs/1540650>22:41
wallyworldaxw: anastasiamac: a minute late23:15
anastasiamack. ping when ready23:18
alexisbanastasiamac, we are on bantering if you would like ot join us23:19
alexisbsaying horrible things about wallyworld23:19
alexisbcherylj, sinzui I see that the maas-spaces branch failed23:40
alexisbany thoughts what is causes the deploys tests failing23:40

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