cheryljhey perrito666, did wallyworld ping you yet about opening bugs for providers with know JES issues?  (this is the destroying multiple environments with the same name issue that was brought up in Oakland)00:08
cheryljmpontillo: you missed the fun :)  most of it was over in #maas00:09
cheryljmpontillo: it was regarding bug 1534795, if you're interested in catching up00:09
mupBug #1534795: unit loses network connectivity during bootstrap: juju 1.25.2 + maas 1.9 <maas-provider> <uosci> <juju-core:Fix Committed by frobware> <juju-core 1.25:Fix Committed by frobware> <https://launchpad.net/bugs/1534795>00:09
perrito666cherylj: nope, in which provider?00:09
cheryljperrito666: all of them with known issues :)00:10
cheryljperrito666: the idea is we open bugs so we can point to them as known issues for 2.0-alpha100:10
mpontillocherylj: thanks; I read through the bug. will wait to hear frobware's findings00:15
menn0thumper: for model migrations, I need to store the connection and auth details for the target controller03:03
menn0thumper: will suggested I made the API that creates the document which holds this stuff take something similar to api.Info03:04
menn0thumper: and I'm tempted to take a tag instead of a username, in case we end up using machine accounts at some stage03:05
menn0thumper: is storing a tag in the DB a no no?03:05
* menn0 wonders about going back to just accepting usernames03:07
thumperwe haven't so far, but I think that this case may be fine03:07
menn0it does simplify some other aspects03:07
thumperfor storing credentials03:07
menn0thumper: it's more flexible if any tag is allowed03:08
menn0i'll do that then03:08
=== akhavr1 is now known as akhavr
mupBug #1536025 opened: LXD provider unable to setup configuration correctly <bouncing> <lxd-provider> <juju-core:Triaged> <https://launchpad.net/bugs/1536025>07:54
anastasiamacjam: imagemetadata worker patch is ready to go... waiting for master to unblock... this should fix the above lxd difficulty \o/08:00
jamanastasiamac: so is that bug a duplicate then?08:03
jamwell, not that one, the previous one08:03
jambug #153601908:03
mupBug #1536019: LXD provider causes imagemedata worker to bounce <bouncing> <imagemetadata> <lxd> <juju-core:Triaged> <https://launchpad.net/bugs/1536019>08:03
anastasiamacjam: i think so... for some providers, this worker should not run... this is what this patch does :D08:04
jamanastasiamac: well, fwiw, i'd love it if we knew about the images that were used for LXD so we didn't have to state in "environments.yaml" that you need to run lxd-images import08:08
jamanastasiamac: we could do the import ourselves, and know when we need to update the base image *and* the templated ones (if we go that far)08:08
anastasiamacjam: sounds reasonable \o/08:09
frobwaredooferlad, ping. sync today?09:06
dooferladfrobware: sorry, yes, still able to talk?09:11
dooferladfrobware: http://pactcoffee.com/spread/JAMES-CMOCKA@cp09:46
dooferladfrobware: you know, just in case09:46
TheMuehehe, the coffee freak. morning btw10:12
frobwaredooferlad, heh. fancy a quick HO, re dns-nameservers. :)10:42
dooferladmorning TheMue!10:42
dooferladfrobware: sure10:42
jamanastasiamac: wallyworld: did we end up leaving deep debugging code in? I'm seeing a lot of "STORAGE FRONT-END" and "STORAGE BACK-END" code triggering.11:28
jambut the content doesn't seem useful11:28
jamas it is debugging a bunch of pointer objects11:28
wallyworldjam: not on purpose11:28
anastasiamacjam: looks like it11:29
jamfacadeCaller: base.facadeCaller{facadeName:"Block", bestVersion: 1, caller: *pointer, closer: *pointer)11:29
wallyworldmust have slipped through review11:29
jamwallyworld: anastasiamac: k. prob should be fixed for at least alpha2, not sure if we've missed alpha111:29
wallyworldthe hope is we got a bless this morning11:29
wallyworldwill make alpha2 for sure11:29
jamI did see a bless11:29
=== ashipika1 is now known as ashipika
frobwarecherylj, beisner: am in the process of writing a conclusion to #1534795. the TL;DR is I don't believe what we've done is broken.12:47
mupBug #1534795: unit loses network connectivity during bootstrap: juju 1.25.2 + maas 1.9 <maas-provider> <uosci> <juju-core:Fix Committed by frobware> <juju-core 1.25:Fix Committed by frobware> <https://launchpad.net/bugs/1534795>12:47
cheryljfrobware: awesome, thank you!12:54
alexisbfwereade, jam, voidspace meeting13:01
voidspacealexisb: omw13:03
TheMueperrito666: answered your question about that drink called Ayran13:39
perrito666TheMue: you drank that?13:40
TheMueperrito666: yes, very refreshing. yogurt and milk with a little bit salt and then beat until frothy13:42
perrito666I should try13:42
TheMueperrito666: it's a national drink in Turkey13:42
TheMueperrito666: they had no beer there, so I asked for something authentic13:42
voidspacedooferlad: tell me more about this ethernet thing you talk of...13:49
dooferladvoidspace: It is like WiFi,  but with wires.13:49
voidspacedooferlad: my wifi never works either... :-)13:49
dooferladvoidspace: :-)13:50
voidspacenot entirely true...13:50
* voidspace lurches to lunch13:50
=== beisner- is now known as beisner
=== StoneTable is now known as aisrael
mupBug #1533750 changed: 2.0-alpha1 stabilization <juju-core:Invalid> <https://launchpad.net/bugs/1533750>14:46
mupBug #1533750 opened: 2.0-alpha1 stabilization <juju-core:Invalid> <https://launchpad.net/bugs/1533750>14:49
mupBug #1533750 changed: 2.0-alpha1 stabilization <juju-core:Invalid> <https://launchpad.net/bugs/1533750>14:52
mupBug #1533750 opened: 2.0-alpha1 stabilization <juju-core:Invalid> <https://launchpad.net/bugs/1533750>14:55
mupBug #1533750 changed: 2.0-alpha1 stabilization <juju-core:Invalid> <https://launchpad.net/bugs/1533750>14:58
cheryljCan I  get a quick review?  http://reviews.vapour.ws/r/3578/14:59
frobwarecherylj, beisner: my observations are in https://bugs.launchpad.net/juju-core/+bug/1534795/comments/3115:12
mupBug #1534795: unit loses network connectivity during bootstrap: juju 1.25.2 + maas 1.9 <maas-provider> <uosci> <juju-core:Fix Committed by frobware> <juju-core 1.25:Fix Committed by frobware> <https://launchpad.net/bugs/1534795>15:12
mupBug #1536215 opened: 1.25.0: deployment times out - system is deployed successfully by maas 1.9 but juju state never transitions from pending <oil> <juju-core:New> <MAAS:New> <https://launchpad.net/bugs/1536215>15:25
mupBug #1536230 opened: backups create help text is wrong about downloading <docs> <papercut> <juju-core:Triaged> <juju-core 1.25:Triaged> <https://launchpad.net/bugs/1536230>15:25
frobwarebeisner, ping15:58
mupBug # changed: 1497312, 1517611, 1525280, 1527349, 1533469, 1533751, 1533792, 1533849, 153621516:01
lazypowerabentley sinzui  - have we tested a 1.20 => 1.25 upgrade?16:03
sinzuilazypower: yes it does work.16:04
lazypowerawesome, i recall 1.22 had some problem child days, so this is great news16:04
abentleylazypower: Yes, we test an upgrade from 1.20 for everything: http://reports.vapour.ws/releases/3522/job/aws-upgrade-20-trusty-amd64/attempt/50816:05
lazypowerthanks for the confirmation sinzui16:05
lazypowerawesome, thanks abentley sinzui  - you just calmed a dusty old charmers fears :D16:06
abentleylazypower: Though the script exits early if the target is 2.0+ because upgrades from 1.20 -> 2.0 are not supported-- you have to go through 1.2516:09
lazypowerabentley makes total sense. this is for a user upgrading from 1.20 => 1.2516:09
beisnerfrobware, pong.  in a mtg atm.16:26
frobwarebeisner, ack. ping me when you have some time; would like to discuss your concerns.16:26
mupBug # changed: 1390585, 1486553, 1527681, 1528217, 1531064, 1534353, 153479516:37
mupBug #1536215 opened: 1.25.0: deployment times out - system is deployed successfully by maas 1.9 but juju state never transitions from pending <oil> <juju-core:New> <MAAS:Invalid> <https://launchpad.net/bugs/1536215>16:37
beisnerfrobware, so i think the lowest common denominator in the topic is this:  bug 1536262   ...and that is why we see what we see in 1.25.3.  thoughts?16:42
mupBug #1536262: dns-* e/n/i are misplaced <uosci> <MAAS:New> <https://launchpad.net/bugs/1536262>16:42
beisnerhi cherylj, frobware, if we can get 1.25.3 into ppa:juju/proposed, that will unblock our openstack CI metal lab.  is that something that is planned in the next day or so?16:55
=== tasdomas` is now known as tasdomas
cheryljbeisner: yes, we're aiming for today.16:57
cheryljbeisner: we just wanted all the dust to settle on the questions around DNS and MAAS16:57
beisnercherylj, frobware - sweet.  yeah so there is still dust but given a sudden realization that indentation in the e/n/i file is meaningless, it's old dust.16:57
ericsnownatefinch: is this what you meant? http://reviews.vapour.ws/r/3579/17:48
natefinchericsnow: yep :)18:08
ericsnownatefinch: thanks for pointing that out :)18:13
natefinchericsnow: no problem.  I've done the exact same thing a half a dozen times... write a whole bunch of code and then realize half of it is covered in the stdlib.18:14
=== marlinc_ is now known as marlinc
=== _stowa_ is now known as _stowa
mupBug #1536324 opened: juju backups restore times out trying to connect to API server <backup-restore> <ci> <juju-core:Triaged> <https://launchpad.net/bugs/1536324>18:55
mupBug #1536324 changed: juju backups restore times out trying to connect to API server <backup-restore> <ci> <juju-core:Invalid> <https://launchpad.net/bugs/1536324>19:29
mupBug # opened: 1536333, 1536336, 1536337, 153634019:29
mupBug #1536345 opened: backups create and backups restore defaults clash <backup-restore> <ci> <papercut> <juju-core:Triaged> <https://launchpad.net/bugs/1536345>19:59
=== mbarnett` is now known as mbarnett
thumperwas the LXD provider available in 1.25 behind a feature flag?21:01
thumperor was it just 1.26/2.0 ?21:02
thumperkatco: ^^?21:02
katcothumper: just 1.26/2.021:02
katcothumper: np. specifically 1.26-alpha221:02
menn0_thumper: I very much doubt that machine-dep-engine is going to merge this week21:16
=== menn0_ is now known as menn0
menn0thumper: there are unblessed changes in master which conflict21:17
menn0thumper: so I have to wait for them to get blessed and then merge and fix the conflicts and then get machine-dep-engine blessed21:18
menn0thumper: there aren't enough days left in the week for that21:18
menn0thumper: I might merge machine-dep-engine right up to latest master in the hope that it'll get blessed. It might save someone less familiar with the changes in the feature branch from having to deal with the conflicts. They look non-trivial.21:21
menn0(next week)21:21
* thumper needs moar coffee21:25
perrito666OT is any of you in the go slack channel, I filled the form to get the invite but didnt :(21:29
natefinchperrito666: I can ping the maintainers about it21:32
cheryljhey davecheney, are you still looking for some bugs to take?21:39
natefinchperrito666: https://gophersinvite.herokuapp.com/21:39
* thumper stops procrastinating and dives into the code21:44
perrito666natefinch: oh, that changed21:56
natefinchperrito666: evidently21:57
=== natefinch is now known as natefinch-afk
perrito666natefinch-afk: tx btw, I am in22:08
mupBug #1536378 opened: resolver loop error in maas-1_8-OS-deployer test <juju-core:Incomplete> <juju-core machine-dep-engine:Triaged> <https://launchpad.net/bugs/1536378>22:11
mupBug #1536378 changed: resolver loop error in maas-1_8-OS-deployer test <juju-core:Incomplete> <juju-core machine-dep-engine:Triaged> <https://launchpad.net/bugs/1536378>22:14
mupBug #1536378 opened: resolver loop error in maas-1_8-OS-deployer test <juju-core:Incomplete> <juju-core machine-dep-engine:Triaged> <https://launchpad.net/bugs/1536378>22:23
thumperI thought that we stopped panicing on unknown series?22:28
thumperI'm using version.MustParseBinary with "3.4.5-zesty-amd64"22:29
thumperand it panics!22:29
perrito666mm, I thought it too22:30
thumperthat's pretty disappointing22:37
davecheneythumper: i can work on that if you like22:42
davecheneybut if you use the Must form, it will panic22:42
davecheneythat's why the Must form exists22:42
davecheneyif you don't want a panic, don't call mustParseBinary22:42
thumperI didn't expext ParseBinary to return an error on unknown series22:43
thumperthat's fine, just gone with "trusty"22:43
davecheneythumper: what should it do if the series is unknown ?22:43
thumperdavecheney: wrt work, cherylj had a particular bug I think22:43
thumperdavecheney: not sure...22:43
davecheneyit would beunwise to return something like "2.0.5-unknown-unknown"22:44
thumperI thought it would have just created a binary with a series it didn't know about22:44
thumperlike "zesty"22:44
davecheney'cos lots of caller expect that any version value is accurate22:44
thumperand not find tools etc22:44
davecheneyhmm, that makes senes22:44
davecheneythat would fit with the notion of Parse22:44
thumperhowever that isn't important just now22:44
thumperI'm working around it22:44
davecheneyit just parses the form provided22:44
davecheneyif you want something else, ParseValidSeries ?22:45
davecheney^ guess22:45
natefinch-afkdavecheney, thumper, katco: I notice I'm invited to this core leads call in 5 minutes.... is that on purpose?22:55
thumpernatefinch-afk: did you go to the earlier one today?22:55
perrito666same question22:55
katconatefinch-afk: it's for if you wish to ask questions about the sprint22:56
natefinch-afkkatco: oh22:56
thumperalexis combined normal weekly team call with team lead call22:56
thumperfor debrief22:56
davecheneynatefinch-afk: thanks for the reminder22:57
katconatefinch-afk: coming?23:03
natefinch-afkkatco: I can come for a bit23:04

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