menn0i'm going to mark 1488581 as Fix Released. Thanks to cherylj's change, the broken test is now passing against in jenkins.01:35
menn0bug 148858101:35
mupBug #1488581: TestFindToolsExactInStorage fails for some archs <blocker> <ci> <i386> <ppc64el> <regression> <storage> <unit-tests> <juju-core:Fix Released by cherylj> <https://launchpad.net/bugs/1488581>01:35
anastasiamacmenn0: cherylj: tyvm!!01:35
menn0master is unblocked again01:36
sinzuimaster cannot be unblcked without a bless01:45
sinzuiPS I just forced a retest to help master get a bless.01:46
anastasiamacsinzui: \o/ tyvm01:50
menn0sinzui: sorry02:14
sinzuiyou are forgiven menn002:14
sinzuionly one job left, then I can sleep02:15
mupBug #1488581 changed: TestFindToolsExactInStorage fails for some archs <blocker> <ci> <i386> <ppc64el> <regression> <storage> <unit-tests> <juju-core:Fix Released by cherylj> <https://launchpad.net/bugs/1488581>02:47
axw_wallyworld: the `storage: add volume status to "juju storage volume list"` card *was* done03:22
axw_just checked, it's in master03:22
axw_moving card from review to previous03:22
wallyworldaxw_: awesome, wanna add a sentence to the release notes?03:22
axw_wallyworld: will do03:22
davecheney./worker/... tests take > 40 minutes to run on ppc6403:28
axw_davecheney: how much is uniter?03:29
davecheney> 600 seconds03:29
davecheneytimed out03:29
davecheneythis fixes the patch that cherylj landed earlier06:20
davecheneynot that her's was wrong06:20
davecheneythis is just the proper fix06:20
mupBug #1488777 opened: Add a wait command <juju-core:New> <https://launchpad.net/bugs/1488777>06:41
bogdanteleagais there a pretty way in golang to insert a slice of strings in the middle of another slice?08:16
bogdanteleagadavechen1y ^^08:16
dimiternbogdanteleaga, https://github.com/golang/go/wiki/SliceTricks08:18
bogdanteleagaI guess it's a = append(a[:i], append(b, a[i:]...)...), wouldn't call it pretty tho08:20
dimiternvoidspace, TheMue, http://reviews.vapour.ws/r/2486/ please take a look - provisioning support for spaces constraints08:32
dimiternbogdanteleaga, the beauty is within :D08:34
voidspacedimitern: looking08:38
voidspacehmmm... coffee first08:40
voidspacedimitern: the travel provider booked me tickets from London to Northampton, and then on the friday back from Northampton to London...08:40
voidspacedimitern: they're buying me new tickets now (for the sprint)08:40
dimiternvoidspace, ok, so all will be sorted out soon hopefully :)08:42
TheMuedimitern: could you tell me why machineSubnetsAndZones()  only uses includeSpaces[0]? (or do I'm looking wrong?)08:44
dimiternTheMue, there is a comment about it08:45
dimiternTheMue, for the MVP work we only use the first positive space and ignore the rest08:45
TheMuedimitern: yeah, read it. but why? simply helping me to understand it. it's a new topic for me. ;)08:46
dimiternTheMue, for simplicity08:48
dimiternTheMue, we want a *minimal* viable product :)08:48
TheMuedimitern: ok, sounds good :)08:48
dimiternTheMue, once we can do deployments within a single space reliably, it shouldn't be much of a problem do expand this to multiple spaces08:49
TheMuedimitern: thx08:50
TheMuedimitern: you've got a review08:52
dimiternTheMue, thanks!08:53
voidspacedimitern: will be a couple of minutes late to standup - on the phone :-/08:59
dimiternvoidspace, sure08:59
voidspacedimitern: lost connection - rejoining09:07
voidspacedimitern: lost connection again - rejoining09:10
voidspacedimitern: struggling to rejoin apparently09:11
voidspacedimitern: dammit - connection lost again09:18
voidspacedimitern: my suggestion is that we store a default, but when the address is requested we look at whether it is an exact match for scope & type09:19
voidspacedimitern: if it isn't an exact match we check for a better match and if there is one we return that and change the default address09:19
voidspacedimitern: so we always return the same one until / unless a better match is found - and then we always return that one09:20
voidspacedimitern: so we *can* change address - but only if we were using a fallback scope or type09:20
voidspacedimitern: does that sound like a reasonable algorithm?09:20
voidspaceI can add it as a comment on the bug to give Ed a chance to comment09:21
dimiternvoidspace, yes, that sounds good09:25
voidspacedimitern: cool09:25
dimiternvoidspace, just to summarize the chat so far: we need a default address (per scope most likely), and a way to only select an exact match per scope09:26
voidspacedimitern: where "per scope" is private / public09:28
dimiternvoidspace, when we don't have a default address yet, just pick the first one; later if we have more than 1 exact match, use the previously stored default09:28
voidspacedimitern: but yes09:28
voidspacedimitern: yes09:28
voidspacedimitern: the algorithm looks like this09:28
voidspacedimitern: first time requested use the first "match" using the current algorithm09:28
voidspacedimitern: subsequent requests, check if the stored default is an exact match - if it is *always* use it09:28
voidspacedimitern: if the default isn't an exact match check if an exact match is now available09:29
voidspacedimitern: if not, use the current default (so we remain stable)09:29
voidspacedimitern: if an exact match is available, store that as the default and use that09:29
voidspacedimitern: subsequent requests will now always see the new default09:29
dimiternvoidspace, how can a previous default address both still exist and not be an exact match?09:30
voidspacedimitern: because if there isn't an exact match on scope / type we allow fallbacks09:31
=== anthonyf is now known as Guest39525
voidspacedimitern: e.g. if preferipv6 is on we can return an ipv4 address if an ipv6 one isn't available09:31
dimiternvoidspace, ah, because the previous default might have been a fallback09:31
voidspacedimitern: so the first part is "if an exact match isn't available still store the fallback as default"09:32
voidspacedimitern: to ensure we always return the same one unless / until an exact match is available09:32
dimiternvoidspace, that all sounds sane to me, but let's add it to the bug and ask dosaboy how does it sound to him09:33
dimiternvoidspace, also, I'd appreciate a review on my PR :)09:35
voidspacedimitern: ok, I've written up my suggestion on the bug and will switch to your PR now09:37
dimiternvoidspace, cheers!09:38
rogpeppetrivial review anyone (no logic changes, just a data change): https://github.com/juju/juju/pull/311009:47
voidspacedimitern: exactly duplicated test setup code in api and apiserver :-/09:48
dimiternvoidspace, it's not quite duplicated :)09:48
dimiternvoidspace, but fair point - it can be put in a common place09:49
dimiternvoidspace, state/testing ?09:49
voidspacedimitern: sounds good.09:49
voidspacedimitern: your call09:52
voidspacedimitern: for *two* use cases it's barely worth it09:52
voidspacedimitern: for three it would definitely be worth it09:52
voidspacedimitern: I won't add it as an issue on the PR, just noting it09:53
dimiternvoidspace, the duplication was bugging me as well, but wanted to make it work first, then polish09:53
dimiternvoidspace, ok09:53
voidspaces.checkStartInstanceCustom(c, m, "pork", s.defaultConstraints, nil, nil, nil, nil, false, nil, true)09:57
voidspacenil, nil, nil, nil, false, nil, true09:57
voidspaceself documenting code be damned!09:57
voidspacedimitern: ah, so this PR only adds support into the dummy provider10:01
voidspacedimitern: EC2 will be a follow up10:01
voidspaceI was looking for where the new mapping was actually used!10:01
voidspaceanyway, looks ok to me - dependent on the EC2 support of course10:02
dimiternvoidspace, yeah, it had to include the dummy provider support10:06
dimiternvoidspace, thanks, will update with the suggestions and set it to land10:06
* fwereade wishes he'd learn to follow his own advice -- dependency.Engine would be much easier to test in pathological cases if I'd thought to write the algorithm without the concurrency11:27
perrito666fwereade: you can tell your self you told you so11:28
TheMuedimitern: btw, your testing stub for spaces is very tricky, but nice. needed some time to get it, now doing the final changes here to handle then enabling and disabling of SupportsSpaces12:37
dimiternTheMue, awesome!12:38
TheMuedimitern: but this leads to a more general proposal. each package should have a doc.go containing only the package statement but above a description about the intention and usage of the package. so it is visible e.g. on godoc.org as well as it is easy to jump into new packages12:40
dimiternTheMue, this is unrelated, but I like it12:47
dimiternTheMue, we should bring it up on the ML for discussion12:47
TheMuedimitern: yep, will do so12:51
sinzuicherylj: is master waiting for a merges to release 1.25-alpha1? or are we waiting on the 3 untested revisions? http://reports.vapour.ws/releases/3008 is bless, but is 3 merges behind tip13:54
natefinchericsnow: thanks for the review of my untrack cmd code.  I responded to a bunch of stuff, but haven't started actually modifying the code yet.13:54
ericsnownatefinch: cool13:54
dimiternvoidspace, hey, how goes the forward port btw?14:15
frobwaredimitern, do you have time to HO for build/test related stuff?14:16
dimiternfrobware, I do, just give me 10m ?14:19
frobwaredimitern, np14:19
sinzuidimitern: per my question in channel earlier, is master waiting for a merges to release 1.25-alpha1? or are we waiting on the 3 untested revisions? http://reports.vapour.ws/releases/3008 is bless, but is 3 merges behind tip14:24
sinzuidimitern: also Lp wont let me update bug 1488576 at the moment. It is a rising problem in the test suite14:25
mupBug #1488576: TestAddresserWorkerStopsWhenAddressDeallocationNotSupported fails on pp64el <ci> <intermittent-failure> <ppc64el> <regression> <unit-tests> <juju-core:Triaged> <https://launchpad.net/bugs/1488576>14:25
dimiternsinzui, I have one PR with I'll set to land in 2 minutes14:26
dimiternsinzui, re that bug - I vote to skip it on ppc6414:26
sinzuidimitern: Ci sees it everyewhere, but is ppc64el most http://reports.vapour.ws/releases/issue/55d89569749a56415476f23b14:27
dimiternsinzui, so if we disable it on ppc64, it should improve things for the time being?14:29
sinzuiyes, but we still risk failure on some other arch until we fix the test14:30
dimiternsinzui, agreed, I'll look into it tomorrow14:32
dimiternsinzui, actually, I'm seeing failures even locally14:34
dimiternsinzui, I'll disable it entirely then14:34
wwitzel3ericsnow: found my bug :)14:34
dimiternsinzui, then tomorrow will dig into it some more14:34
sinzuidimitern: yeah. when I first found the bug, it was only on ppc64el. we now have several runs and see it everywhere. That is was I was trying to say in the bug when Lp was giving who timeouts14:35
wwitzel3ericsnow: I didn't remove the Workloads list from the meta struct in the charm library and our Definitions call loops through meta.Workloads (which was empty)14:35
sinzuidimitern: once your current PR is merges (assuming a bless) do we haver all the features in place for a release?14:36
dimiternsinzui, I have no others of mine14:38
dimiternsinzui, and I believe nothing critical remains from our stuff14:39
sinzuithank you dimitern14:39
dimiternfrobware, *whew* sorry for the delay, let's get in a HO now?14:40
frobwaredimitern, ok14:43
ericsnowwwitzel3: ah, glad you caught that14:46
marcoceppihey core guys, there's an email on the main juju list with some issues around huge mongodb, odd errors, and 4+gb log files Could someone take a look?15:08
marcoceppihey core guys and gals*15:08
marcoceppihey core ppl*15:08
mgzpc fail15:09
marcoceppiactually trying to break old habbits of calling everyone guys15:09
mgzer... as in 'politial correctness'15:09
* marcoceppi is not sloth15:10
mgzit's good to try :)15:10
mgzI basically think of guys as gender neutral these days, it's how it seems to be used15:10
mgzI've seen women using it to address a mixed group, but I guess not a all-female group15:11
cheryljI use it to address my lady-friends15:11
* katco thinks guys is fine and uses it to address my lady-friends as well15:12
natefinchor all-y'all15:12
katconatefinch: personally hate that colloquialism15:12
natefinchkatco: lol me too15:12
cheryljI don't think I've ever used y'all un-ironically15:12
cheryljand I'm from texas, y'all!15:13
marcoceppiI made someone mad over the weekend by using guys in my typical gender neutral fashion, so peeps is it from now on15:13
natefinchcherylj: me either, but I'm a Yankee15:13
mgzI use peeps ironically, except sometimes I forget the irony15:13
marcoceppieverything I say is ironic15:13
natefincheven that!15:13
marcoceppianyways, core peeps, there's that email, I'm not sure what to tell him over then "try to upgrade your production openstack environment to use juju 1.24.5"15:14
natefinchmarcoceppi: looking15:19
marcoceppinatefinch: thanks!15:24
natefinchmarcoceppi: first thought is that it might be networking problems.  timeouts usually mean networking15:27
sinzuidimitern: cherylj : are you happy with master tip? Is this waht you want to release? Ci will test this soon: https://github.com/juju/juju/commits/master15:50
cheryljsinzui: that works for me, but I don't know if there are other merges we're waiting on.15:51
cheryljcmars, katco, are there things you're wanting in  1.25-alpha1?15:51
sinzui^ katco are you really hear to call the cut of 1.25-alpha1?15:51
mupBug #1489053 opened: rabbitmq-server charm fails on cluster-relation-changed when using openstack provider <juju-core:New> <https://launchpad.net/bugs/1489053>15:52
katcosinzui: i'm here15:52
katcocherylj: sinzui: sorry been out sick... moonstone didn't have anything for 1.2515:52
ionutbalutoiuHey! I have an idle juju machine with a charm deployed on it. Everytime I reboot the machine, config-changed gets executed when machine comes up. I pressume this is the normal behaviour, right ?15:54
natefinchionutbalutoiu: I believe so.  config-changed hooks get run a lot.  The code in them should be written with that in mind.15:57
voidspacedimitern: oh yeah, meant to tell you - sorry16:09
voidspacedimitern: it's already on master16:09
mupBug #1489053 changed: rabbitmq-server charm fails on cluster-relation-changed when using openstack provider <rabbitmq-server (Juju Charms Collection):New> <https://launchpad.net/bugs/1489053>16:22
voidspacenatefinch: for bugfixes, which branch should we target?16:23
voidspacenatefinch: nice haircut by the way16:23
natefinchvoidspace: thanks16:35
natefinchvoidspace: uh... bug fixes for what?16:35
voidspacenatefinch: I am working on a juju-core bug16:38
voidspacenatefinch: how far back are we doing bug fixes (what versions are we still supporting)?16:38
voidspacethe bug is in 1.2016:38
voidspacebut I don't think we're supporting that16:39
voidspacekatco:  do you know how far back are we doing bug fixes (what versions are we still supporting)?16:48
voidspacekatco: I'm working on a bug reported against 1.20, but I'm pretty sure we're not still releasing 1.2016:48
katcovoidspace: yeah i'm pretty sure we aren't releasing anything < 1.22. sinzui comments?16:49
sinzuikatco: we are not. also we have nothing scheduled to 1.22. only 1.24 has plans for a release16:50
sinzuivoidspace: ^16:50
voidspacesinzui: thanks16:50
voidspacekatco: thanks too16:50
katcovoidspace: o/ sorry we don't get to talk much16:50
sinzuiPS, don't merge into 1.23, it wont pass without other backports16:50
voidspacekatco: yeah :-/16:50
voidspacekatco: but o/ from across the water...16:51
katcovoidspace: :) how is the newbie family member doing?16:51
voidspacekatco: he's good. Keeping us busy, very demanding of attention - desparate to walk and eat but too young for either (5 months no teeth)16:52
voidspacebut very adorable of course16:52
voidspacekatco: how's yours?16:52
katcoaw glad to hear it :)16:52
katcowell she gave the family another lovely chest cold16:52
katcoso she's recovering, but overall doing good16:52
voidspacehe's lovely, much more sociable than Irina was - who still doesn't really like people very much :-)16:52
katcostarted walking a few weeks ago16:53
voidspacekatco: heh16:53
voidspacekatco: ah, chaos time :-)16:53
katcohah yeah16:53
katcovoidspace: isn't it weird how their personalities can come through at such a young age16:53
voidspaceyeah, lovely to watch personality develop16:53
voidspaceIrina is in the "why" and "what" phase - she asks about 428 times a day what a word means16:54
voidspacewhich is cool16:54
voidspaceand inevitably every answer has another word she wants explained16:54
voidspaceso we end up in these long exhausting chains of explaining things16:54
voidspacebut it's great that she's so thirsty to learn16:55
katcoyeah i bet that's neat16:55
katcoanxiously waiting for that stage16:55
voidspaceso far (aged four) Irina has got more and more fun as she grows16:56
katcoi am definitely a >= toddler person. not overly excited about babies16:56
katcovery excited to be able to communicate better16:56
voidspacehehe - me too mostly16:56
voidspaceyep, it's *so* much better when you can explain things to them and they can understand16:57
katcoi was just thinking yesterday when she was not feeling great16:57
voidspacewe went on a big road trip round Europe - Irina was fine in the car, but you can't explain to a baby why they're in the car and how long it will be for16:57
cmarscherylj, nothing specifically. i want 1.25 to branch :)16:57
katcoshe was crying and i was wishing she could tell me what was wrong16:57
voidspaceyeah, that's hard16:57
katcovoidspace: haha so true16:57
=== mrjazzcat is now known as mrjazzcat-afk
mupBug #1489087 opened: certificate verify failed <juju-core:New> <https://launchpad.net/bugs/1489087>17:55
sinzuikatco: bug 1489131 jeopardises our release of 1.25-alpha1 tomorrow. I think cherylj fixes something similar to this yesterday.19:14
mupBug #1489131: BootstrapSuite.TestRunTests fails on non-amd64 archs <blocker> <ci> <ppc64el> <regression> <test-failure> <unit-tests> <juju-core:Triaged> <https://launchpad.net/bugs/1489131>19:14
katcocherylj: ring any bells?19:14
cheryljkatco: let me take a look19:15
sinzuicherylj: I would phrase this as have you seen anf fixed a mistake like this before?19:15
cheryljsinzui: it looks like it's in the same vein as the blocker yesterday, but it's in a different spot.19:16
sinzuicherylj: I wonder if someone cargo culted one of the areas you fixed before your fix merged19:16
cheryljsinzui: I see davechen1y was in the offending file 2 days ago.19:18
cheryljhmm, I'm puzzled why this wouldn't have been hit before...19:26
cheryljit's not as a result of a recent change, as far as I can tell19:26
cheryljwait, this could be due to Dave's changes yesterday19:27
cheryljyeah, I think it is.    Either way, it's an easy fix.19:29
mupBug #1489142: cpu-power constraint conflicts with with instance-type when trying to launch a t2.medium <juju-core:New> <https://launchpad.net/bugs/1489142>19:36
jcastrowe really need help with this bug19:36
jcastroit's currently blocking a demo we need to deliver tomorrow and this bug kind of reached out to bite us.19:37
arosalescritical issue here for Mark's demo tomorrow at Silicon Valley OpenStack ^19:37
katcojcastro: arosales: TAL19:37
mupBug #1489131 opened: BootstrapSuite.TestRunTests fails on non-amd64 archs <blocker> <ci> <ppc64el> <regression> <test-failure> <unit-tests> <juju-core:In Progress by cherylj> <https://launchpad.net/bugs/1489131>19:37
mupBug #1489142 opened: cpu-power constraint conflicts with with instance-type when trying to launch a t2.medium <juju-core:New> <https://launchpad.net/bugs/1489142>19:37
katcojcastro: is the behavior any different if you do add-machine first?19:38
jcastrotrying now19:38
jcastrokatco: no change, same result19:40
katcojcastro: k, peeking around the code19:40
katcojcastro: what version is this?19:42
jcastrokatco: anything that just lets us deploy to a t2.medium, even if it's ugly, would do the trick19:44
marcoceppikatco: even explicitly setting cpu-power=0 in the global constraints for the environment I still get no instance types in us-west-2 matching constraints "cpu-power=10019:44
marcoceppi      instance-type=t2.medium"19:44
cheryljReview request for the blocker if someone could take a look: http://reviews.vapour.ws/r/2492/19:45
cheryljmarcoceppi: what do you get when you run juju get-constraints?19:49
cheryljyou can unset all constraings with set-constraints "" I think19:49
cheryljconstraints, even19:49
cheryljjcastro: can you unset the constraints with juju set-constraints "" ?19:52
jcastrohe's on the phone, one sec19:52
marcoceppicherylj: it's empty when I first ran it19:53
cheryljwell that's interesting19:53
marcoceppicherylj: it's now cpu-power=0 which has no effect19:53
marcoceppicherylj: it's always been empty, fwiw :)19:54
cheryljhmm, wonder where it's coming from, then19:54
mramm{ // General Purpose, 3rd generation.19:54
mrammName:     "t2.medium",19:54
mrammArches:   amd64,19:54
mrammCpuCores: 2,19:54
mrammMem:      4096,19:54
mramm// Burstable baseline is 40% (from http://aws.amazon.com/ec2/faqs/#burst)19:54
mrammCpuPower: instances.CpuPower(40),19:54
mrammVirtType: &paravirtual,19:54
mrammtry setting it to less than 4019:54
marcoceppimramm: you can't19:55
marcoceppijuju deploy cassandra --constraints="cpu-power=0 instance-type=t2.medium" -n 319:55
marcoceppiAdded charm "cs:trusty/cassandra-3" to the environment.19:55
marcoceppiERROR ambiguous constraints: "cpu-power" overlaps with "instance-type"19:55
cheryljand if you just do --constraints="instance-type=t2.medium", that doesn't work?19:56
katcocherylj: see bug 148914219:56
marcoceppicherylj: no, I get this error19:56
mupBug #1489142: cpu-power constraint conflicts with with instance-type when trying to launch a t2.medium <juju-core:New> <https://launchpad.net/bugs/1489142>19:56
marcoceppino instance types in us-west-2 matching constraints "cpu-power=100 instance-type=t2.medium"19:56
katcomarcoceppi: specifying both cpu-power and instance-type is the correct error19:56
marcoceppikatco: cool, figured it was19:56
katcomarcoceppi: specifying instance-type is the mystery atm19:57
marcoceppiI would have never tried if I didn't get the above error first :)19:57
katcoyeah hehe19:57
mrammand you really need t2.medium?19:58
marcoceppikatco cherylj mramm http://paste.ubuntu.com/12201761/19:58
jcastroyes, the demo needs a t2.medium19:58
jcastrocan't be another instance type19:58
marcoceppimramm: it's the only amazon instance that matches the orangebox openstack demo of 2 cpus and 4 gb of ram19:58
natefinchI wonder if CPU-power is specified as an environment level, and we're just combining them dumbly19:59
natefinchenvironment-level constraint that is19:59
cheryljnatefinch: that's what I thought too, but we should be able to see that with get-constraints which marcoceppi says is empty19:59
mrammcan you get a t2.medium by JUST using cpu-power=4020:00
marcoceppicherylj: wellthere are global default constraints, that never show up, ie: cpu-power=100 cpu-cores=1 mem=1.5g, etc20:00
marcoceppimramm: trying that now20:00
katcomarcoceppi: mramm: yeah just going to suggest that20:00
marcoceppiuh, i got this http://paste.ubuntu.com/12201785/20:01
mrammahh VPC... dreaded VPC20:02
marcoceppit2 instnances don't have this requirement though20:02
marcoceppithis is an m4 isntance it tried to launch20:02
marcoceppimy guess m4.large20:02
katcomarcoceppi: try "arch=amd64 cpu-cores=2 mem=4096 cpu-power=40"20:03
katcomarcoceppi: (basically just specifying the things declared by default in a t2.medium)20:03
katcoericsnow: wwitzel3: natefinch: all hands20:04
katcoperrito666: ping ^^20:04
wwitzel3ahh, yep, one more line ....20:04
marcoceppiif this doesn't work I'll spin the instances by hand and manual provider them in with ssh20:04
marcoceppikatco: http://paste.ubuntu.com/12201804/20:05
mramm"It’s interesting to note that Amazon is making T2 instances VPC-only. This is a mechanism to move newer workloads to VPC by default."20:05
marcoceppiwtf it didn't say that on the page I was looking at20:06
marcoceppiokay, so how do I get a vpc juju thingy20:06
mrammYou must launch your T2 instances into a virtual private cloud (VPC); they are not supported on the EC2-Classic platform.20:06
wwitzel3katco: what's the hangout? it isn't on my calendar20:06
mrammdirectly from the amazon docs20:06
marcoceppifoadthx amazon20:06
katcowwitzel3: no hangout atm20:07
natefinchkatco: there's nothing in my calendar... what all hands?20:07
katconatefinch: wwitzel3: the discussion happening in this chat right now20:07
natefinchkatco: oh, sorry, misunderstood.20:08
marcoceppiokay, so we have the instance, it's just I need a vpc now20:08
katconatefinch: wwitzel3: try and troubleshoot the first attempt in bug 148914220:08
mupBug #1489142: cpu-power constraint conflicts with with instance-type when trying to launch a t2.medium <constraints> <juju-core:New> <https://launchpad.net/bugs/1489142>20:08
marcoceppiand juju+vpc =...?20:08
marcoceppiI'm guessing good to go no issues at all fire away, but I'll wait20:08
mrammmarcoceppi: do you have an account with default VPC?20:10
mrammthat is the easiest path forward20:10
marcoceppiI don't think so? my account was created like 4 years ago20:10
mrammyea, you'd need a newer account to use20:10
marcoceppiI do have a new account though20:10
marcoceppithat I have access to20:10
mrammI'm not sure how much of VPC support has actually landed in 1.2420:11
natefinchat best, we need to handle this case better.  Saying there's a conflict is a huge red herring20:11
jcastroyeah, let's sort that after we unblock marco20:11
katconatefinch: focus on the 1st use-case... the instance-type constraint doesn't seem to be working20:12
mrammnatefinch: agreed there is lots here to fix20:12
marcoceppiGoing to see if this new account has default vpc, in which case I can use the constraints katco gave to get unblocked20:13
mrammmarcoceppi: cool20:13
katcomarcoceppi: jcastro: here's the algo. for performing the selection: https://github.com/juju/juju/blob/master/environs/instances/instancetype.go#L9520:16
marcoceppimramm katco so with a default vcp, will all my instances just luanch in it?20:19
katcomarcoceppi: i haven't looked at it recently, but i think i remember reading that20:20
marcoceppikatco: seems so, bootstrap node seems to be in it20:20
mrammkatco: marcoceppi: I believe that is correct20:21
natefinchdidn't we used to display instance type in juju status?20:25
marcoceppifor the love of20:25
marcoceppi'cannot run instances: Virtualization type ''hvm'' is required20:25
marcoceppi      for instances of type ''t2.medium''. Ensure that you are using an AMI with virtualization20:25
marcoceppi      type ''hvm''. For more information, see http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/virtualization_types.html20:25
marcoceppi      (InvalidParameterCombination)'20:25
marcoceppilooks like I'm just not going to win today20:25
marcoceppican I give juju an AMI?20:27
marcoceppiI know the answer is "no", but like, can I actually do it?20:27
natefinchmarcoceppi: lol20:27
marcoceppiI need this ami-afd5c09f for hvm apparently20:28
natefinchmarcoceppi: http://cdn.meme.am/instances/55580985.jpg20:29
jcastrowe're going to launch them by hand and then just add-machine via ssh20:30
natefinchcan you not just use a different machine size?20:31
natefinchlike... bigger?20:31
jcastrothe demo requires a t2.medium20:31
arosalesnatefinch, we need to have a specific instance size for benchmark comparison20:32
bogdanteleagamarcoceppi: yes, you could give juju a ami to use, but you need to modify some code in core20:32
arosalesbogdanteleaga, modifying code in core is a no-op for a demo tomorrow20:33
bogdanteleagaamazon only accepts image metadata that's signed20:33
bogdanteleagathat would be the problem here20:33
bogdanteleagaif you could get that, it would also work20:33
natefinchso, instance-type works. just not with t2.... so probably it's the VPC thing causing an error that we interpret incorrectly.20:38
katconatefinch: wondering if instance-type is specified, should we even be setting a default cpu power? isn't that implied by instance-type?20:40
jcastrowhen you do it with a new account it works because amazon defaults to vpc for users newer than dec 201320:40
marcoceppikatco: I say no, I the user supplied an instance-type, it should be the only thing that matters20:40
jcastroonce you get past that though it's trying to use the pv image instead of the hvm image20:40
natefinchkatco: yeah, instance-type is supposed to override everything20:40
natefinchkatco: my guess is that the code that adds CPU-Power is coming later in the call stack and appending it, without considering if instance-type is set20:41
natefinchkatco: although I don't think it's actually hurting us20:41
katconatefinch: pushing patch now that addresses that20:41
natefinch(aside from being confusing)20:42
bogdanteleagagot a questions about constraints since we're on the subject: is there a place to define default constraints/provider?20:42
bogdanteleagaI found that at least on aws windows machines need 35GB20:43
katconatefinch: well, i'm wondering if we didn't set cpu power to a default if the search algo could find a match20:43
natefinchbogdanteleaga: any constraints set when you bootstrap become environment-wide constraints20:43
sinzuikatco: natefinch : do either of you have a minute to review cherylj's http://reviews.vapour.ws/r/2492/20:43
bogdanteleaganatefinch, yes but ideally we'd have this the default for windows instances20:43
katcosinzui: trying to resolve something blocking a demo tomorrow20:43
natefinchkatco: my guess is that amazon is returning "no instances" because you don't have the default VPC, and we're just assuming it's because of the constraints mentioned20:43
natefinchkatco: but certainly we shouldn't be adding the cpu-power when instance-type is set20:45
natefinchkatco: so that's a fix to make regardless20:45
natefinchkatco: logically backwards... should only be if instancetype *is* nil20:45
katconatefinch: doh... damn sick head20:46
MakyoHaving some problems with panics on CI - anyone else encountered similar? http://juju-ci.vapour.ws:8080/job/github-merge-juju/4494/console20:46
natefinchkatco: this is why we have reviews :)  (and also tests, but I understand not writing the test in a crunch)20:47
katconatefinch: recheck20:48
natefinchkatco: got a typo in the comment there.... think you were typing in the wrong window20:48
katconatefinch: again20:49
natefinchkatco: ship it!20:50
katcomarcoceppi: i don't suppose a 1.24.6 beta would help at all?20:51
jcastrowe're past the vpc problem for now20:51
jcastrojust wrestling with the hhvm issue now20:51
katcojcastro: k20:51
jcastrot2.medium wants an ami that is built for hhvm, but juju is handing it normal pv ami's20:52
katconatefinch: i'm going to wait to merge this until ian weighs in as well. it looks like he touched a lot of the constraints code20:52
jcastroso .. the current plan is he just launched the instances by hand in the aws gui20:52
jcastroand then is manually adding the machines via ssh20:52
jcastroand then deploying cassandra onto that20:52
marcoceppiwwitzel3: http://paste.ubuntu.com/12202091/20:52
natefinchjcastro: manual provider should do well enough20:53
natefinchjcastro: at least for last minute demo purpsoes20:53
sinzuiMakyo: the juju unittests are poorly isolated and timed. We often see many attempts needed to merge. Because of the poor isolation, it is possible a test change you your branch unhinged the  dblogSuite.TearDownTest and dblogSuite.TestUnitAgentLogsGoToDBWithJES tests :(20:54
Makyosinzui: ack, thanks.  I'll do a bit more digging around what changed.20:55
marcoceppiwwitzel3: https://bugs.launchpad.net/juju-core/+bug/147815620:55
mupBug #1478156: tabular format does not give enough details about machine provisioning errors <charmers> <juju-core:Triaged> <https://launchpad.net/bugs/1478156>20:55
=== natefinch is now known as natefinch-afk
katcowallyworld: hey can you TAL at http://reviews.vapour.ws/r/2493/diff/# and see if it seems sane?21:27
davechen1ycherylj: thanks for the fix22:57
davechen1yfyi, i am testing these, not just comitting them blidly22:58
davechen1yon ppc6422:58
davechen1ybut my ppc64 machine is so slow I cannot run all the tests22:58
davechen1yso I have to work only in the areas I think are affected22:58
davechen1ysorry i missed this one22:58
wallyworldanastasiamac: standup?23:18

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