== Meeting information == * #ubuntu-meeting Meeting, 18 Jun at 15:03 — 15:45 UTC * Full logs at [[http://ubottu.com/meetingology/logs/ubuntu-meeting/2015/ubuntu-meeting.2015-06-18-15.03.log.html]] == Meeting summary == === Lightning round === The discussion about "Lightning round" started at 15:03. === AOB === The discussion about "AOB" started at 15:31. == Vote results == == Done items == * (none) == People present (lines said) == * slangasek (71) * pitti (47) * infinity (41) * sil2100 (21) * stgraber (18) * robru (17) * bdmurray (15) * barry (13) * doko (13) * ubottu (4) * meetingology (3) * cyphermox (3) == Full Log == 15:03 #startmeeting 15:03 Meeting started Thu Jun 18 15:03:22 2015 UTC. The chair is slangasek. Information about MeetBot at http://wiki.ubuntu.com/meetingology. 15:03 15:03 Available commands: action commands idea info link nick 15:03 [TOPIC] Lightning round 15:03 $ echo $(shuf -e barry doko stgraber jodh bdmurray slangasek caribou infinity sil2100 robru cyphermox pitti) 15:03 doko jodh caribou robru bdmurray pitti barry cyphermox sil2100 slangasek stgraber infinity 15:04 doko: hi, around? 15:05 is jodh even still officially in the team? 15:05 hmm, and we have a change to this list since last time... 15:05 slangasek: i think you need to update your shuf :) 15:05 next time should be: 15:06 echo $(shuf -e barry doko stgraber bdmurray slangasek caribou infinity sil2100 robru cyphermox pitti 15:06 yep 15:06 nd no caribou here today 15:06 robru: 15:07 one sec 15:07 * CI Train: 15:07 - added script for scanning overlay PPA versions and comparing to wily archive; ensure that matching version numbers have matching binary hashes 15:07 * CI Train Charm: 15:07 - stop clobbering creds with empty files if creds misconfigured 15:07 - add relation for bileto 15:07 * Bileto: 15:07 - fixed some postgres-specific bugs 15:07 * Bileto Charm: 15:07 - add basenode support 15:07 - add relation for ci-train 15:07 * Train mojo Spec: 15:07 - added relation between ci-train and bileto 15:07 - various iterations on postgres configuration 15:07 (done) 15:08 robru the magician, charming with his mojo! 15:08 heh 15:09 bdmurray: 15:09 robru: clobbering creds with empty files> I don't suppose that helps the postgres issues at all? 15:10 continued to work on improvements to apport-retrace to check launchpad for packages not available in archive or on ddebs.u.c 15:10 worked with pitti to get my apport use-lp branch merged (done!) 15:10 worked on hacking in ppa support to apport-retrace 15:10 pushed an apport branch (with a PPA hack) for the retracers to use 15:10 updated daisy config for armhf 15.04 retracers for overlay ppa 15:10 submitted RT to have daisy / apport updated in staging 15:10 slangasek: no that's unrelated, that's on the ci-train side. #is doesn't have creds stored the same way we do in staging and so the charm was clobbering live creds with empty files. 15:10 investigation into the right way to add ppa support to apport 15:10 SRU verifications of python-pip bug fixing LP: #1324391 (fail, then pass) 15:10 Launchpad bug 1324391 in python-pip (Ubuntu Trusty) "pip 1.5.4 import an invalid dependencies " [High,Fix committed] https://launchpad.net/bugs/1324391 15:10 discussed with mvo python-apt origin information and PPAs 15:10 discussion with slangasek regarding overlay-ppa and old packages 15:10 investigation into a phased-updater OOPS 15:10 short week as I was in Rochester! 15:10 * doko is a bit late ... 15:10 ✔ done 15:11 doko: hi, your turn 15:11 slangasek: that thing was probably related to the train outage we had on Friday when the cred files went missing 15:11 ok 15:12 five me 5min 15:12 alright then. pitti: 15:12 systemd: 15:12 - create script to build debs for current systemd upstream trunk (into PPA, and running all autopkgtests locally), for a more proper trunk CI 15:12 - fix various build system and udev regressions in trunk 15:12 - enable net.ifnames persistant network names by default 15:12 autopkgtest: 15:12 - set up ProdStack/Canonistack with IS for cloud-based autopkgtest running, and create autopkgtest cloud runner PoC 15:12 - various small improvements to adt-run 15:12 - revive armhf/ppc64el worker nodes after outage 15:12 misc: 15:12 - review and land bdmurray's apport branch for downloading older sources/debs from LP 15:12 - build and test fresh vivid langpacks 15:12 - postgresql: prepare new upstream security/bug fix releases for all supported Ubuntu releases 15:12 - reproduce and analyze misconfigured/broken encrypted swap in LVM install mode (#1453738); in progress 15:12 - various bug fixes in open-scsi, udisks 15:12 plan: 15:12 - systemd 221 is around the corner; unlike the previous two versions this should now be a breeze to land thanks to all the new CI 15:12 - continue working on cloud-based autopkgtest runner 15:12 - find some time to look into networkd integration with resolvconf and ifup.d/ 15:12 ^D 15:13 doko or me? 15:13 barry: go ahead, it hasn't been 5 minutes yet :) 15:13 barry: 5 mins aren't over yet 15:13 sounds like a monty python sketch... 15:13 short week due to pto 15:13 debuntu: debian bug #776026; python-nose-exclude 0.2.0-4; zope.security 4.0.3-1; virtualenv 13.0.3-1 (ongoing), wheel 0.24.0-2; python-pip 1.5.4-1ubuntu3 for trusty; 15:13 Debian bug 776026 in src:wheel "wheel: please make whl files reproducible" [Wishlist,Fixed] http://bugs.debian.org/776026 15:13 si: 2.5.1 to the overlay; struggling with landing 3.0.1 in wily via train (and getting derailed) 15:14 started working on the python3.5 transition plan 15:14 other: upgrade bisecting and other debugging for LP: #1464365 15:14 Launchpad bug 1464365 in xorg (Ubuntu) "Resolution is incorrect; screen mostly occluded" [Medium,New] https://launchpad.net/bugs/1464365 15:14 --done-- 15:14 - openjdk-9 fixes for ppc64el and arm64 15:14 - updated GCC 5 transition plan 15:14 - openjdk maintainer interviews 15:14 - preparing uploads for gcc 4.8, 4.9 and 5.x release candidates 15:14 - started doing some merges 15:14 - finally gcc-4.8 and binutils SRU's in trusty, uploaded cross packages 15:14 - uploaded python3.4 SRU's 15:14 (done) 15:15 cyphermox: ping 15:15 sil2100: I'm on vacation, not actually there :) 15:15 cyphermox is still on vacation 15:15 Ah, ok :) 15:15 sil2100: 15:15 - Landing team work, silo coordination, preparing landing e-mails 15:15 - Prepare OTA-4 release notes 15:15 - OTA-4 release: 15:15 * Copying images and setting auto-phasing for the period of approx one day 15:15 * Preparing community OTA-4 images, promoting those after basic QA 15:15 * Promoting ubuntu-developer images 15:15 * Preparing non-delta images for arale 15:15 - Identifying the system-image situation, preparing landing 15:15 - Leading the RTM status meeting 15:15 - Updating documentation regarding package twins 15:15 - Further work on commitlog generation 15:15 - Coordinating the Unity8 big landing 15:15 - Lack of sleep and overall tiredness for the whole week 15:16 Holiday tomorrow (Friday the 19th) 15:16 (done) 15:16 Do you celebrate every Friday the 19th? 15:17 it's a very famous movie in Poland 15:17 slangasek: (you're up) 15:18 * helping unblock the libnettle transition; found blockage due to a mir-related API change that was causing gst-plugins-bad1.0 to FTBFS as of vivid release, working to unwind that through bug #1465958, now waiting for a platform-api landing 15:18 bug 1465958 in platform-api (Ubuntu) "gst-plugins-bad1.0 FTBFS: mirclient headers needed" [High,Confirmed] https://launchpad.net/bugs/1465958 15:18 * post mortem for the various issues we've run into over the past two months with the overlay ppa not being as featureful as the derived distribution out of the box 15:18 * closing in on a decision for the Java maintainer role 15:18 * new job opening in the process of being posted, should be visible tomorrow 15:18 (I know) 15:18 (done) 15:18 stgraber: 15:18 - Was out on Friday. Now back in Montreal. 15:18 - LXC/LXD 15:18 - Working on LXD socket activation systemd units. 15:18 - Made a first version of the LXD snap. 15:18 - Working on the CI infrastructure for LXC-related projects a bit. 15:18 - Spent quite a lot of time debugging a weird race condition in LXD. 15:18 - Code reviews, bug triaging, other admin paperwork 15:18 - Alpha-1 15:18 - Some prepwork for alpha-1, mostly sorting out nusakan <-> tracker issues 15:18 (done) 15:18 - Dealing with several transitions in wily 15:18 - Not one, but *two* emergency kernel security updates 15:18 - Fixed kernel autopkgtesting 15:18 - General AA/SRU stuff 15:18 - Looking into kernel changes we might need to build armhf on arm64 15:19 - Sobbing uncontrollably over the loss of mvo 15:19 - Mitigating the above with the 'yay pitti' happy dance 15:19 - debian-installer and HWE work 15:19 (done) 15:19 :) 15:19 ♩ \o/ ♫ ♪ 15:19 infinity: that's to the tune of 'hey mickey', right? 15:19 infinity: where's the youtube video of that dance? 15:20 (happy dance for fixing kernel tests) 15:20 I think pitti wants to take over UTF-8 summary ending lead. :) 15:20 barry: It's an easter egg in d-i, go find it. 15:20 heh 15:20 any questions over status? 15:20 infinity: do you have to fix 5 bugs before it reveals itself? 15:21 oh, and doko's binutis/gcc SRUs got released in trusty 15:21 Yeah, which means we can probably undo a hack in linux-lts-vivid. 15:21 (only ignoring 3 and 6 autopkgtest regressions respectively) 15:21 * infinity makes a note. 15:22 autopkgtest regressions for trusty? 15:22 doko: yes; not caused by either of your SRUs, just caused by letting autopkgtests bitrot for a year in trusty before we started looking at them again 15:22 some of them being network-related failures 15:22 slangasek: were you able to make that document with the side-by-side comparison of overlay and derived distro for olli? 15:23 some being mysql tests that fail because time doesn't stand still and SSL certificates expired 15:23 ahh, I see. where can you see these? 15:23 sil2100: in progress; will be done this morning 15:23 I sent a summary to u-devel@; mostly because of tests relying on quirks/bugs of the null runner which we used back then 15:23 Thanks! 15:23 doko: you probably can't get a link to the specific set anymore now that we've released the SRUs; there's nothing that you should need to look at however 15:24 the most interesting one was a lintian testsuite failure claiming that a binary was now a corrupted elf object - but that error started happening a week *before* binutils was uploaded to trusty-proposed 15:24 pitti: Speaking of, did you want back on ~ubuntu-sru and ~ubuntu-release so you can have a bit more direct control over this madness? 15:24 infinity: I need ~release for that, right? 15:24 pitti: release for devel series, sru for SRUs. 15:24 infinity: you are just going to let this new guy on these teams? 15:25 pitti: We split the hints across the teams, just like we split the queues. 15:25 bdmurray: He's emeritus on both teams. :P 15:25 infinity: He might have forgotten how to do things! 15:25 That's a chance I'm willing to take. 15:25 I just select all and click "accept" 15:26 Okay, not willing anymore. 15:26 pitti: I think you mean select all and click Reject :) 15:26 I'm not yearning for more work, just to manage stuff that's innocently stuck in -proposed a little better 15:26 heh 15:27 doko: fwiw if you want an overview of failing autopkgtests, in theory https://jenkins.qa.ubuntu.com/view/Trusty/view/AutoPkgTest/ is some kind of one 15:27 pitti: Team membership doesn't imply forced duties, though it might get you pinged occasionally for help with something. Anyhow, your call, no one's voluntold into these teams. 15:27 slangasek, thanks, not so nice as update_excuses ... 15:27 infinity: right, please add me 15:27 pitti: select all and click "reject" with "Spite" as the reason, everyone will think you're infinity :) 15:28 slangasek: Did anyone investigate the lintian regression and sort out what it really was? The last time lintian had a testsuite explosion like that, it really was a (weird) toolchain regression. 15:28 doko: update_excuses gives you the overview for packages that are in progress. for SRUs that were already accepted, it no longer applies 15:28 oh, we don't have archives for SRUs 15:28 we do have them for devel 15:29 pitti: Reactivated in both. 15:29 infinity: no. what I did sort out was that the timing didn't line up with the binutils change, which was what had triggered the test rerun 15:29 actually, I lie: http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses/trusty/ 15:29 ^ should have all the old excuses? 15:29 infinity: (nor the gcc change; first lintian test failure was May 4, SRU accepts were May 13-14) 15:30 pitti: oh, it should? interesting 15:30 slangasek: Sure, timing says it clearly wasn't *that* upload, still would be nice to figure out the cause. Maybe I'll poke later in my copious free time. 15:30 conveniently un-clickable, but at least there 15:30 doko: ^^ so there is an archive of the excuses if you really care; but with my SRU hat I already reviewed them and declared them to be false positives 15:31 [TOPIC] AOB 15:31 anything else? 15:31 Sure. Since we already hijacked the meeting for sru/release stuff... 15:31 yes, right now we need to mostly ignore trusty, unless we upload a couple of SRUs to fix tests 15:31 slangasek, stgraber, pitti : ~ubuntu-release only has one Admin (me), which is suboptimal. Anyone want to volunteer to be a second Admin? 15:31 are we actually to where we're meant to be wrt not regressing the testbeds? 15:32 infinity: you can give me bits 15:32 slangasek: since utopic, yes; trusty had a completely different infrastructure 15:32 slangasek: Done. 15:33 pitti: my meaning is: are we at the point now where the testbed we're using to test trusty SRUs properly models what we were using at the time of trusty release 15:33 (per the discussion in Austin) 15:33 slangasek: I think he's saying "close as it can get", since the runner is completely different, and we can't fix that. 15:33 ok 15:33 I did see some test failures that appeared to be regressions in the network policy 15:34 i.e., use of proxy + accessing Canonical network resources still returning a failure 15:34 slangasek: they now have build-essential pre-installed; but e. g. the "tests don't have their build deps installed" behaviour is still differnet 15:34 that too 15:34 but there's not much I can do about that, we don't have unrestricted network there 15:34 Network policy is about to change again, so that's an ongoing battle. 15:34 But hopefully we can do it smoothly. 15:34 I'm not asking for an unrestricted network 15:34 infinity: in scalingstack you mean? 15:34 I'm asking for the network policy to actually match what I understood to have been agreed with CI :) 15:35 pitti: Yeah. Though, we can probably do better with the move to scalingstack. 15:35 which was "external resources on the Canonical network ok (but not yet implemented); truly external resources outside of our control, not ok" 15:37 slangasek: ah, we still have the old "anything goes via proxy" policy ATM 15:37 barry: ^^ this also impacts your system-image tests of course, so if you want to know when your autopkgtests will be allowed to work... :) 15:37 ah, that wasn't what you last told me, if that's the plan, then I'll have to turn off a bunch of tests in the LXC testsuite with the next upload 15:37 pitti: oh, ok. I saw some test failures that implied that things were not working, including using the proxy 15:37 was that "no arbitrary net access" already decided? (I object rather strongly..) 15:37 I object to that too, unless Debian adopts the same policy. 15:38 unless "external resources on the Canonical network ok" includes "squid.internal" in which case, I've got what I need 15:38 Cause hacking every test from Debian is ungood. 15:38 slangasek: yeah. although i haven't gotten that far yet, i did re-enable the autopkgtests that do smoketesting against s-i.u.c 15:38 tests relying on arbitrary external resources are unreliable tests 15:38 well, we would just change "one out of 1000 runs fails" with "all runs fail" 15:38 TBH, the unreliability of tests pales compared to the unreliability of our infrastructure 15:38 to the point that I can't even remember a single case 15:39 I mean wrt. remote net access, not in general 15:39 it's also not necessarily a bad thing if you learn that a test relying on an external resource is failing 15:40 if I have to retry a failed net-accessing test twice a year, I'll be reeeeeeally happy :) 15:40 stgraber: well, at least for the moment it's possible to access via the proxy 15:40 (except when this randomly doesn't work) 15:40 slangasek: We did note that there are valid uses for tests talking to external resources, but often those don't relate to uploads, but should be daily "does my IM client software still work" tests. 15:41 slangasek: ok. I got a bunch of e-mails about test failures and the log looked like no network connectivity but it wasn't triggered by one of my uploads so I didn't really look into the failure 15:41 infinity: yes 15:41 slangasek: But if we figure out how to cater to that case, we still need to be able to talk to external resources to do it. 15:41 infinity: the conclusion was "this doesn't belong in an autopkgtest run as part of proposed-migration" 15:42 slangasek: Sure, "... as part of p-m", I agree with, but we're building infra that should be flexible and reusable. 15:42 it can be run under a different tenant with a different network policy 15:42 * infinity shrugs. 15:42 using the same charm on the same cloud 15:42 Anyhow, stgraber's use case also seems reasonable. Unless we want to host all his blobs in our network just to make the test 100% reliable instead of 99%, which seems like overengineering for a problem we don't have. 15:43 stgraber: I heard something to the effect that Canonical would be doing internal hosting of lxc images; is that the plan? 15:43 slangasek: nope 15:43 infinity: ^ or at least I don't think it's sensible to think about this while 20% of our tests fail due to random infrastructure problems 15:44 LXD will be using the cloud images at some point in the near future, but nothing's changing for LXC 15:44 stgraber: ah, of course 15:44 pitti: I like the theory that we'll make the infra five-nines reliable, so other problems become more obvious. 15:44 and LXD's own testsuite already doesn't rely on network access at all 15:44 pitti: But, yeah, let's try to get there first. 15:44 ok I think we've discussed this to death 15:44 shall we release our captive audience? 15:45 +1 15:45 #endmeeting Generated by MeetBot 0.1.5 (http://wiki.ubuntu.com/meetingology)