Tuesday, 2015-06-23

*** dims has quit IRC00:55
*** dims has joined #openstack-relmgr-office00:57
*** dims has quit IRC02:36
*** AzherKhan has joined #openstack-relmgr-office02:47
*** david-lyle_ has quit IRC04:03
*** mestery has joined #openstack-relmgr-office04:19
*** mestery has quit IRC04:49
ttxOhai! Office hours opening08:02
ttxI'll get some coffee, get yourself comfortable in the mean time08:02
ttxstevebaker: around?08:06
ttxflaper87, SergeyLukjanov: same question08:12
flaper87ttx: I am around08:12
ttxLooking at zaqar liberty-108:13
flaper87yup, I think we're almost there but there's a feature I'd like to get in for L-108:13
ttxflaper87: we now have a script that auto-targets completed blueprints and removes liberty-1 target from incomplete blueprints. Let me dry-run it08:13
ttxsee what that would do08:14
flaper87ahh nice08:14
flaper87ok ok08:14
ttxjust a sec, damn LP API forces script to retrieve all blueprint ever created08:14
ttxScript would clear milestone target from : https://blueprints.launchpad.net/zaqar/+spec/persistent-transport08:15
ttxis that the last feature you'd like for L1 ?08:15
flaper87mmh, nope, that's one but there's also pre-signed urls08:17
flaper87we're short in time to make it happen and it's very likely it'll be part of L-208:17
flaper87but I don't want to loose hope08:17
ttxwell, there are two days left08:17
flaper87ttx: don't kill my hope08:17
flaper87PLEASE DON'T!08:17
ttxyou have a blueprint for pre-signed URLs ?08:17
ttxif yes we should target it08:17
flaper87I have a spec for sure but there should be a blueprint as well. I remember creating it.08:18
flaper87lemme get it for you08:18
ttxAnything else that should appear on that list ? Like another major feature that was landed since kilo FF ?08:19
ttxAlso, what's the status of pre-signed URLs ? Under code review ?08:20
flaper87nothing else08:21
flaper87ooook I'll move pre-signed URLs to l-208:21
* flaper87 moved it08:22
ttxOK, still having hope for persistent-transport though ?08:22
ttxOn the bug list at https://launchpad.net/zaqar/+milestone/liberty-1, anything we should block on ?08:23
flaper87that's under review08:23
ttxI don't see anything critical, so I guess no08:23
flaper87no critical bugs08:23
ttxI'll move all incompletes to liberty-208:23
flaper87the list should be up-to-date08:23
ttxOK, https://launchpad.net/zaqar/+milestone/liberty-1 looks good now, shows that the only thing we are blocking on is Persistent transport08:24
ttxlet us know over the next two days when to tag08:24
ttxprobably when you give up all hope08:25
ttxflaper87: and have a good day !08:25
ttxflaper87: oh btw that will be tagged... 1.0.0b108:26
flaper87ttx: LOL, don't take the hope away from me :(08:28
flaper87sure thing, I'll be back here and let you know08:28
ttxflaper87: if you have something else we should wait on, you can add the milestone target to it08:28
* johnthetubaguy is lurking for when ttx is ready for nova fun08:29
ttxthat will put it on our radar08:29
ttxjohnthetubaguy: always ready for some nova fun08:29
ttxjohnthetubaguy: So let's see what the script would do at this point08:29
ttxscript needs to parse 1912 nova blueprints08:30
ttxtakes a bit of time08:30
ttxjohnthetubaguy: http://paste.openstack.org/show/316093/08:31
ttxanything that is completed that doesn't belong in liberty-1 ?08:32
ttxanything that will be cleared that actually shouldn't ?08:32
johnthetubaguytaking a quick look08:32
johnthetubaguyso the completed ones all look updated already: https://blueprints.launchpad.net/nova/+spec/online-schema-changes08:33
johnthetubaguyis there something missing from their current state?08:33
johnthetubaguywhat I mean is, I though all those completed ones are already approved for liberty and targeted to liberty-108:34
ttxright... it's just that you can't read the series field using the API, so I just set it to be sure08:35
ttx(you can set it, you can't read it)08:36
ttxYou can't be more sad than I am about that08:36
johnthetubaguythats fun08:36
ttxThe only way to "read" it is to retrieve all blueprints in a series and check if it's in08:36
ttxI figured we can spare that and just set it again08:37
johnthetubaguyyeah, OK, now I get your question, makes sense08:37
johnthetubaguyso the answer is that they all look good to me08:37
ttxanything on the second part of the list that we should NOT clear ?08:37
johnthetubaguyttx: you are only clearing the milestone and not the series I am guessing?08:38
johnthetubaguythats cool then08:39
johnthetubaguyI mean there are all in needscodereview, but I don't see many of them merging in the next few days08:39
ttxwe can always fish them back if they do08:40
johnthetubaguyyeah, makes sense08:40
ttxAlso not opposed to tag right now rather than come back in two days08:40
ttxlet's run script08:40
johnthetubaguyyeah, script run sounds good08:40
johnthetubaguyso I kinda want to ask around about major blooper bugs a bit more, just in case08:41
ttxon the bugs side, can I move incomplete bugs to l2 ?08:41
ttxoh, no incomplete bugs08:41
ttxall good there08:41
johnthetubaguycool, I checked those yesterday, there wasn't anything blocking there08:42
ttxOK https://launchpad.net/nova/+milestone/liberty-1 is now cleaned08:42
ttxanything blatantly missing from that list of new features ?08:43
ttxi.e. something we'd retroactively create a BP for ?08:43
johnthetubaguyI haven't seen anything08:45
johnthetubaguybut there are lots of patches, and I can't claim to have looked too closely at *everything*08:46
ttxalright, I think we are good then08:46
ttxno big deal anyway08:46
johnthetubaguyyeah, we can add those later if needed08:46
ttxJust let us know sometimes between now and Thursday when to tag. It's fine to be early.08:46
johnthetubaguyOK, cool. I will ask around for bug issues, and get in touch later on08:47
johnthetubaguyttx: liking the new process, it seems much more efficient, good work on that08:48
ttxtooling still a bit rough around edges :)08:48
ttxjohnthetubaguy: have a good day!08:49
ttxSergeyLukjanov: around?08:50
SergeyLukjanovttx, yup08:50
SergeyLukjanovttx, good morning08:50
ttxSergeyLukjanov: morning!08:50
SergeyLukjanovttx, I've cleaned the l1 page - https://launchpad.net/sahara/+milestone/liberty-108:50
SergeyLukjanovttx, so, we're waiting for 4 CRs to be merged before l108:50
ttxlet's see what my script thinks about it08:51
ttxit hasn't much to say08:51
ttxare those 4 likely to get merged in the coming day(s)08:52
SergeyLukjanov3 are in the gate now and 1 will be approved in a few hours08:52
SergeyLukjanovso, I think we should be ready later today08:52
ttxLooks like you have things under control as always08:53
ttxI won't hold you any longer then08:53
SergeyLukjanovthx, hope so (mean re control :) )08:53
ttxSahara will be tagged 3.0.0b108:54
ttxSergeyLukjanov: do you still release the extra repos at the same time ?08:54
SergeyLukjanovttx, btw I've tagged sahara-image-elements and sahara-extra w/ 3.0.0a0 and switched vrsion to 3.0.0 in setup.cfg08:54
SergeyLukjanovttx, yeah08:54
ttxWe could move them under release management the same way we release the neutron-*aas stuff at the same time as neutron08:55
ttxfood for thoughts post-l1 I guess08:55
ttxthose are generally ready by the time openstack/sahara is ready, right ?08:55
SergeyLukjanovyeah, ok, I think it makes sense08:56
ttxok, I'll add a note about that08:56
SergeyLukjanovI'm tagging them right after see tag in sahara08:56
ttxand come back to you after L1 about it08:56
SergeyLukjanovokay, thx08:56
SergeyLukjanovttx, we're now discussing separation of integration tests to the separated repo - sahara-tests w/ separated release cycle, most likely tempest-style08:57
SergeyLukjanov(just a note)08:57
ttxhmm, ok08:57
johnthetubaguyttx: when you get a sec, someone is talking about missing tags, although I have very little context on the issue: https://storyboard.openstack.org/#!/story/2000300 I think lifeless was talking to them09:04
lifelesscontext is in -infra09:06
johnthetubaguylifeless: cool, thanks, sorry about that, got wrong end of the stick09:07
lifelessde nada09:07
ttxlifeless: completely different discussion, wanted to ask you about the "fix the world" plan and progress there -- still on track ? Anything you need help with ?09:13
ttxsince you seem to touch so many things those days, I can't keep up09:13
lifelessttx: I need https://review.openstack.org/#/c/194401/ landed09:14
lifelessto unblock https://review.openstack.org/#/c/189250/09:15
lifelessand the stuff above it09:15
lifelessthe pip stuff is done and in develop, awaiting a release09:15
lifelessthe devstack constraints patch is done but in WIP waiting for the constraints to be in requirements09:16
lifelessI might make that a Depend-On soon09:16
lifelesswe haven't got the experiment back-facing jobs up09:17
lifelessbut I figure until we have the constraints patch passing experimental there's no rush09:17
ttxso in summary, good progress, but still in the maze of interdependent changes09:17
lifelesstwisty twisty mazes09:17
ttxgreat, thx for the update09:17
*** dims has joined #openstack-relmgr-office10:06
sdaguelifeless: I'm going to redo 194401 because it's not actually that obvious what the difference is today10:27
*** AzherKhan has quit IRC10:53
openstackgerritMerged openstack-infra/release-tools: Update milestone.sh to support new versioning  https://review.openstack.org/19406811:41
ttxdhellmann: do you mind if I rebase the type:library / type:service / release:managed patch chain ?12:37
dhellmannttx: I can do it if you're otherwise busy12:38
ttxI actually just did the rebase, ready to push12:38
dhellmannok, go for it12:38
ttxhmm, got an error12:39
ttxNo changes between prior commit c20e16b and new commit a3f435912:39
ttxmaybe I need to push them one by one12:41
dhellmannttx: when I update master I don't see any changes. Why do they need to be rebased?12:44
ttxthey were hitting merge conflicts all over. Have trouble reaching Gerrit so haven't refreshed that though12:45
* ttx rechecks12:46
ttxhttps://review.openstack.org/#/c/192193/ needs rebase12:46
dhellmannthat's weird, none of the others do12:47
ttxok, I'll redo it12:48
dhellmannttx: ok, when I check out your commit (and all of mine) and rebase that whole stack I do get a conflict12:48
dhellmanngit review -d 192193 && git rebase master12:49
ttxyeah, probably yours don't trigger it but mine on top triggers 3-way merge fail12:49
ttxi'll see if I can work around it without pushing a new patchset below it12:50
SergeyLukjanovttx, dhellmann sahara is now ready for the liberty-1 tag12:55
ttxSergeyLukjanov: be there in a minute12:55
dhellmannSergeyLukjanov: I'll let ttx follow up with you12:56
dhellmanndims: I'm building a list of unreleased oslo changes...12:57
dhellmannthis report takes longer every time I run it, since we keep adding libs :-)12:57
dimsso we start off by list_oslo_unreleased_changes.sh12:57
dhellmanna lot of those requirements updates are format churn, so I don't think we need to release anything based only on those changes12:58
dimsmessaging/middleware - maybe. vmware - they are not ready yet. db - waiting for victors.12:59
dhellmannactually, let's work in https://etherpad.openstack.org/p/library-releases so we can make notes12:59
dhellmannI pasted the script output in there already12:59
dhellmannconcurrency looks like it could use a release13:00
dhellmanndims: config looks like mostly doc changes13:01
dimsyes, concurrency does13:01
dimsfor concurrency we may need to cut something off of stable/kilo to support a nova security fix that tonyb is working on13:02
dhellmannok, that same script can produce a report of unreleased changes in stable branches, too13:02
dimsyes, lets do the master first13:03
ttxok, fixed it, that was weird.13:03
ttxsorry for the noise13:03
ttxSergeyLukjanov: o/13:03
ttxLet's try trhis new milestone.sh script13:04
dhellmanndims: is "CORS Middleware defers to server response" a feature or bug fix?13:05
dhellmannin middleware13:05
ttxdhellmann, SergeyLukjanov: milestone.sh proposes to tag 3.0.0b1 for shara. All clear ?13:05
dhellmannttx: checking13:06
dhellmannttx, SergeyLukjanov : according to https://etherpad.openstack.org/p/liberty-initial-semver-values that is correct13:06
dhellmanndims: how about that rootwrap change, do we need that for debugging something somewhere?13:06
dimsdhellmann: no, just a good to have13:07
dhellmannok, I'll leave it up to you whether to do it13:07
SergeyLukjanovyup, correct13:09
dimsdhellmann: looks like we got through the list13:09
dhellmanndims: not quite?13:17
ttx"Tarball generated at sahara-"13:17
ttxTag is 3.0.0b1 but we get sahara- built.13:17
*** openstack has quit IRC13:17
*** openstack has joined #openstack-relmgr-office13:19
dhellmanndims: yes, see lines 5-10 for format13:19
dimsack. just making sure. i'll build up that list13:19
dhellmanndims: ok, I think that's all of them, do you want to doublecheck my work?13:21
dimsdhellmann: was checking as you were pasting13:21
dhellmannI thought you probably were :-)13:22
dhellmannok, so then you stick that text in a file and pass it to release_many.sh, normally13:22
dhellmannyou're set up to use release_library.sh already, right?13:22
dhellmann(launchpad login, etc.?)13:23
dimsdhellmann: i believe so13:23
dhellmannok, let's do one to test, and then you can use release_many.sh on the others13:23
dhellmanndims: maybe use oslotest, since that's least likely to be noticed immediately if there's a problem13:24
dimsdhellmann: ack. will do it in a little bit and report back13:24
dhellmanndims: sounds good -- after the script runs it will leave a file in relnotes/ named for the lib and version containing the release notes email. It's an actual email, so you might be able to just send it using sendmail (I pass it to msmtp on OS X). If the format doesn't work for you, we can look at tweaking it to make it more suitable.13:26
dimssounds good dhellmann. thanks!13:26
dhellmannafter the email flood from a while back, I decided that sending the emails should be a separate step :-)13:26
openstackgerritThierry Carrez proposed openstack-infra/release-tools: Pre-versions are now $VERSION.0b1  https://review.openstack.org/19465913:34
ttxdhellmann: I'll run that version now ^ and retag13:35
dhellmannttx: +2a13:35
ttxSergeyLukjanov: I'll retag so that the tag corresponds to the tarball version13:36
ttxThat means you should push a tag to the other repos.13:36
ttxSorry about that, I always seem to miss episodes of atht fun PEP440 vs. PBR saga13:38
ttxarh, fail in the upload13:39
* ttx fixes again13:40
openstackgerritDoug Hellmann proposed openstack-infra/release-tools: Only use tput when we are writing to a terminal  https://review.openstack.org/19466113:41
openstackgerritMerged openstack-infra/release-tools: Pre-versions are now $VERSION.0b1  https://review.openstack.org/19465913:41
SergeyLukjanovttx, yeah, I know this feeling ;)13:41
SergeyLukjanovttx, so, the upcoming tags will be and then 3.0.0 for release?13:43
ttxthat is my understanding13:43
SergeyLukjanovokay :)13:44
ttxdamn, upload_release needs a fix too. All those tools need a serious rearchitecture now :)13:44
openstackgerritThierry Carrez proposed openstack-infra/release-tools: upload_release.py should use $VERSION.0b1 too  https://review.openstack.org/19466213:46
ttxused successfully to upload sahara's tarball ^13:46
ttxSergeyLukjanov: bug 1444348 was apparently fixed between the two tags ?13:47
openstackbug 1444348 in Sahara kilo "[DIB][CDH] 404 extjs not found" [High,Triaged] https://launchpad.net/bugs/144434813:47
ttxshowing as FixCommitted in https://launchpad.net/sahara/liberty/liberty-1 but Fixreleased in https://launchpad.net/bugs/144434813:48
openstackLaunchpad bug 1444348 in Sahara kilo "[DIB][CDH] 404 extjs not found" [High,Triaged]13:48
* ttx sobs13:49
ttxoh, got it13:50
ttxthe juno task was targeted to liberty-1 (don't ask why that's even possible)13:50
ttxso the bug was listed twice in the milestone page13:51
ttx(don't ask why someone thought that could ever be a good idea)13:51
ttxSergeyLukjanov: all set ^13:51
ttxsorry for the bumps in the road13:51
ttxdhellmann: I'll start pinging people from the East/Central section of that etherpad13:55
ttxdhellmann: I did add a few answers for your questions in the checklist13:55
dhellmannttx: ok13:56
ttxdhellmann: Also taking notes of what went wrong / we'll need to work on in a section at the bottom13:56
dhellmannI noticed the new section with notes13:56
*** gordc has joined #openstack-relmgr-office13:57
ttxgordc: welcome!13:57
gordcttx: sorry. completely forgot about the liberty-1 stuff13:57
ttxthat happens13:57
ttxI'd like to take a few minutes to prepare https://launchpad.net/ceilometer/+milestone/liberty-1 before we tag13:58
gordcsounds good13:58
ttxI have a script that will suggest a few changes13:58
ttxjust a sec while I ruin it13:58
ttxor run it13:58
ttxThe script suggest adding the following completed blueprints to the page:13:59
gordcthe pipeline items we can remove... they will not be contained in L113:59
ttxand then suggests we drop the 3 incomplete blueprints there13:59
ttxIf you agree I can run the script and it will do the magic13:59
gordcah, that alarm item was merged a while ago (was wondering what it was)14:00
ttxyou agree that the 3 incomplete BPs on that page aren't likely to make it in the next hours or day ?14:01
gordcyes, the 3 bps can be dropped for L1, won't be merged today or this week even14:01
ttxalright running script14:01
gordcwe can also drop the one bug item attached to me. that can be merged but probably won't be merged unless i ask someone14:02
gordcit's low priority anyways so it's not super important for L114:02
ttxanything blatantly missing from the list of completed features ?14:03
ttxwe can retroactively create a blueprint for any major feature that didn't get a blueprint14:03
gordci'll take a quick glance14:04
ttxgordc: any blueprint / bugfix in the pipe that should still block the liberty-1 tag ?14:04
ttxIf not I'll move that in-progress bug in the page to liberty-214:04
gordcttx: all the bps listed seem to be fine. i'm not tracking anything other than those.14:05
gordcfrom bug pov, there are quite a few committed but i've yet to target to L114:05
ttxno need14:06
ttxI have a script that will pick them up automatically when I tag14:06
gordcah cool.14:06
gordcyes, please do that... and we ca nmove the inprogress bug to liberty214:06
ttxgordc: any reason to hold on the tag ? If it's not now, we can wait one or two days14:06
ttx5.0.0.0b1 since liberty final for ceilometer will be 5.0.014:07
dimsdhellmann: what's the command line you use for msmtp to send out one email?14:07
dhellmanndims: just a sec...14:07
gordcttx: i wasn't tracking anything critical. i just got back from a business trip so let me give a quick ping to those that were around to see if anything i missed14:07
ttxgordc: sure, no hurry. Just ping us here when you are good to go14:08
ttxif you want to wait on something, you can add the milestone target to it so that it appears on the page as a blocker14:08
ttxuseful for trackjing what we should hold the tag over14:08
dhellmanndims: http://pastebin.com/NaDhxuDA14:08
ttxgordc: thx!14:09
gordcttx: something i've always been meaning to ask. how do i target something to an older milestone after it's been cut?14:09
gordcttx: seems like it only lets me point to something in future.14:09
ttxgordc: you have to reopen the milestone14:09
ttxand then reclose it14:09
ttxI should write a script to do that14:09
dimsdhellmann: thanks14:10
gordcttx: ah i see.. and i can reopen a milestone or is that only something release team has?14:10
ttxgordc: manually you can go to the milestone page and set Active back to yes. The reload the bug page14:10
ttxthen set the milestone14:10
ttxthen put back milestone to Inactive14:10
gordcttx: ah i see. i'll give that a try14:10
ttxI'll make a target_bug.py <bug#> <milestone>14:11
ttxI think I have it somewhere14:11
gordcttx: also, just confirmed with the small team, nothing i missed since i was gone, so no blockers for L114:11
ttxgordc: ok then I think I'll proceed14:11
gordcttx: sounds good. thanks for the reminder14:12
ttxgordc: will ping you when completed, should take 2 min14:13
SergeyLukjanovttx, thank you!14:13
ttxdhellmann: could you +2a https://review.openstack.org/#/c/194662/ so that I run the scripts off master ?14:14
SergeyLukjanovttx, is it ok that there both tags in sahara - 3.0.0b1 and
ttxSergeyLukjanov: 3.0.0b1 is clearly superfluous. Asked on -infra and they can't really remove it now14:17
SergeyLukjanovttx, should we remove the tag or let's just ignore it?14:18
SergeyLukjanovttx, IMO it's safe to keep it14:18
ttxyep, not the first f*ed-up tag in history14:19
SergeyLukjanovttx, yeah :)14:20
openstackgerritThierry Carrez proposed openstack-infra/release-tools: Fix version determination in corner cases  https://review.openstack.org/19467514:22
ttxdhellmann: and this one too ^14:22
dhellmannttx: looking14:23
dhellmannttx: +2a to both14:24
ttxceilo tag on its way14:24
ttxmestery, nikhil_k, redrobot: ping14:25
openstackgerritMerged openstack-infra/release-tools: upload_release.py should use $VERSION.0b1 too  https://review.openstack.org/19466214:25
* thingee lurks14:26
ttxthingee: we can go over Cinder now if you have 5 min14:27
thingeettx: yes please :)14:27
openstackgerritMerged openstack-infra/release-tools: Fix version determination in corner cases  https://review.openstack.org/19467514:27
ttxhttps://launchpad.net/cinder/+milestone/liberty-1 looks pretty clean already14:27
ttxlet me see what the script suggests14:28
thingeettx: fixed those unassigned bps14:29
thingeettx: tag and don't look back!14:29
ttxyep, no additional suggestion14:29
ttxwon't ask you if you have anything missing from the list, it's massive already14:30
ttxnothing to wait for ? Should we just tag now ?14:30
thingeettx: feeling pretty good, yeah go for it.14:31
ttxok, will do as soon as ceilo is done14:31
ttxwill be
thingeettx: I wanted to raise that cinder client is in bad shape for deployments using proxies14:31
nikhil_kttx: around when you are free14:32
thingeeversion discovery isn't working well without a configuration option server side that only surfaced in Kilo.14:32
ttxnot really new, right ?14:32
ttxgordc: done @ https://launchpad.net/ceilometer/+milestone/liberty-114:33
thingeettx: well I guess people are using it now, and deployments like HP and rax are having support issues come in14:33
ttxtagging cinder14:33
thingeettx: https://bugs.launchpad.net/python-cinderclient/+bug/146416014:33
openstackLaunchpad bug 1464160 in python-cinderclient "ERROR: Bad Request (HTTP 400) with cinder 1.2.1" [Critical,In progress] - Assigned to Mike Perez (thingee)14:33
gordcttx: cool cool. thanks!14:34
thingeettx: two options, revert version discovery or backport https://review.openstack.org/#/c/159374/ to juno which introduces a config opt14:34
gordcttx: i'm going to try re-activating, deactivating a milestone. please shout if this affects you.14:34
thingeettx: the config opt doesn't change default behavior luckily... anyways figured it being a long shot with this introducing a config opt and juno being set to security only14:36
ttxthingee: the alternative sounds worse14:37
ttxthingee: reverting version discovery in kilo is more disruptive14:38
thingeettx: ok, wanted to gauge from you if would be worth raising in the mailing list. I'll post something today14:38
ttxwarrants a thread imho, yes14:39
thingeethanks that's all for me.14:39
redrobotttx pong14:45
ttxthingee: cool thx14:45
ttxredrobot: hey! Let me talk to nikhil_k real quick first14:45
ttxnikhil_k: around now ?14:45
redrobotttx sure14:45
ttxgoing once14:46
ttxgoing twice14:46
ttxredrobot: you win14:46
ttxGoal is to beat https://launchpad.net/barbican/+milestone/liberty-1 into shape before tagging14:46
nikhil_koops, got called in another meeting. I can wait14:47
ttxredrobot: let's see what my script suggests14:47
ttxredrobot: it suggests to defer multi-user-functional-tests since it's incomplete14:47
ttxbut then maybe it's close and could use that extra day(s) before the deadline ?14:47
redrobotttx no, I think it'll be fine.14:48
ttxredrobot: so I should move it off the milestone ?14:49
redrobotttx looks like your script did?14:49
ttxoh.. yes, I missed --dryrun there14:50
ttxoh well14:50
ttxredrobot: is there any significant feature landed in barbican that we'd want to show off on that page ?14:51
ttxWe could retroactively create a BP for it14:51
openstackgerritDoug Hellmann proposed openstack-infra/release-tools: Add script for targeting bugs from the command line  https://review.openstack.org/19468814:51
redrobotttx not yet. :-\  ... there's a couple that are really close.  If we wait to tag until Thursday we can probably have two bps land14:52
ttxredrobot: I think that would be great14:53
redrobotttx ok, I'll be back on Thursday14:53
redrobotttx thanks!14:54
ttxredrobot: maybe we should target those likely features to liberty-1 and track them, and decide early Thursday ?14:54
redrobotttx ok, will do14:54
ttxredrobot: please add both there asap14:54
openstackgerritDoug Hellmann proposed openstack-infra/release-tools: Add --no-clear flag to adjust_blueprints.py  https://review.openstack.org/19468914:55
ttxnikhil_k: have to jump on a phone meeting. Maybe dhellmann can process you14:55
dhellmannttx, nikhil_k: I'm about to step away, too :-/14:56
dhellmannnikhil_k: I'll be back online in ~2 hrs for my office hours period14:56
nikhil_kdhellmann: ttx : Sure, I can be online at 2pm ET14:57
dhellmannnikhil_k: ok, if ttx doesn't take care of you before then, I'll catch up with you as soon as I'm back online14:57
nikhil_kdhellmann: have a dentist appt so will have to be afk from 3pm ET (Iam assuming you are in ET :) )14:57
dhellmannnikhil_k:  yes, I'm in ET14:57
nikhil_kdhellmann: sounds good. thanks14:58
nikhil_kHope atlanta is not hotlanta this summer14:58
dhellmannnikhil_k: ever summer :-/14:58
morganfainbergdhellmann: ping re https://review.openstack.org/#/c/173972/ and https://bugs.launchpad.net/keystonemiddleware/+bug/146398815:00
openstackLaunchpad bug 1463988 in keystonemiddleware "oslo.config version error in kilo" [Undecided,New]15:00
dhellmannnikhil_k: if you want to get a head start, you could look at https://launchpad.net/glance/+milestone/liberty-1 and verify the status of the blueprints and bugs -- it looks like there are a couple of bugs that aren't closed, yet, so we need to decide whether to hold the milestone tag for those or whether to retarget the bugs15:00
morganfainbergare we ever unblocking the pin/cap for kilo there?15:01
nikhil_kdhellmann: thanks. I will clean it up and find blockers if so15:01
dhellmannmorganfainberg: we need to fix the cap without raising the minimum, which I think will require turning off the requirements check job for the repository15:01
dhellmannnikhil_k: sounds good15:01
morganfainbergor can we just fix stable/kilo g-r to not raise the minimum?15:02
dhellmannnikhil_k: the script didn't find any untargeted but completed blueprints, so that's good, but you may want to review any open blueprints that should have been closed, too15:02
morganfainbergbecause it seems like we're in a catch22.15:02
nikhil_kdhellmann: sure, there was one private bug  that I moved to l215:03
dhellmannmorganfainberg: I would have to look at the details for that particular package, I'm just giving general guidance15:03
morganfainbergif we depend on that minimum elsewhere in OS we should be setting the right minimum15:03
dhellmannmorganfainberg: we can't raise the minimum in a stable branch as a matter of policy15:03
dhellmannmorganfainberg: we can change the upper because that doesn't force distros to repackage15:04
morganfainbergright - my point is it seems like if the minimum is wrong, it's wrong everywhere15:04
dhellmannnikhil_k: what about bug 1453047?15:04
openstackbug 1453047 in Glance "ValueError: Tables "artifact_blob_locations,artifact_blobs,artifact_dependencies,artifact_properties,artifact_tags,artifacts,image_locations,image_members,image_properties,image_tags,images,metadef_namespace_resource_types,metadef_namespaces,metadef_objects,metadef_properties,metadef_resource_types,metadef_tags,task_info,tasks" have non utf8 collation, please make sure all tables are CHARSET=utf8" [High,New] https://launchpad.net/bugs/1453047 - Assigned to Flavio Percoco (flaper87)15:04
morganfainbergor we ended up with the wrong stable/kilo sha when branching15:04
dhellmannmorganfainberg: let me actually read the bug15:04
dhellmannmorganfainberg: so designate is downgrading oslo.config?15:05
nikhil_kdhellmann: not blockers. artifacts still experimental15:05
dhellmannnikhil_k: ok, we're going to close the milestone by thursday, so do you think that's going to be merged or should it be retargeted?15:06
morganfainbergdhellmann: the issue is we have stable/kilo with an uncapped oslo.config in keystonemiddleware. it looks like *some* packages have it capped15:06
morganfainbergdhellmann: keystonemiddleware installs earlier, then causes issues. that is my read15:06
morganfainbergand looking at that patch, the minimums don't looks like they are affected - i might be mis-reading though15:07
morganfainbergoh except oslo.config15:07
dhellmannmorganfainberg: ok, I'm about to walk out the door, so I may need to think about this more later today. As I said, we need a fix that doesn't involve raising the minimum versions, but we should be able to apply caps in places that need them. However, that probably brings those repos out of sync with the global requirements in kilo, which means turning off the requirements check job to be able to land the patches.15:07
morganfainbergdhellmann: no worries.15:07
morganfainbergdhellmann: let me re-read i don't think that patch is affecting minimums15:07
morganfainbergdhellmann: just looking at it15:08
nikhil_kdhellmann: I moved it to l2. Now the l1 list for Glance bugs and BP seems consistent. Please feel free to cut a release when appropriate.15:08
dhellmannmorganfainberg: ok, it has been updated and that job was turned off, so I think it's safe to approve now15:08
morganfainbergdhellmann: ok i'll check with you later today before approving - so i'm post coffee and you're not running out the door15:09
dhellmannmorganfainberg: please get someone else familiar with stable requirements to double-check me, but I added a =215:09
* morganfainberg doesn't want to break the world15:09
morganfainbergmaked WIP and issued a recheck. catch you later on dhellmann15:10
dhellmannnikhil_k: do you have any extra bugs that should be targeted to L-1?15:10
dhellmannmorganfainberg: ack, thanks15:10
*** isviridov_away is now known as isviridov15:10
nikhil_kdhellmann: no open bugs. I guess your script would catch any that already merged and don;t have a milestone set?15:11
dhellmannnikhil_k: yes15:11
dhellmannnikhil_k: lots: https://bugs.launchpad.net/glance/+bugs?field.searchtext=&orderby=-importance&search=Search&field.status%3Alist=FIXCOMMITTED&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_commenter=&field.subscriber=&field.structural_subscriber=&field.tag=&field.tags_combinator=ANY&field.has_cve.used=&field.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.has_patch.used=&field.has_branches.used=&fiel15:11
dhellmannnikhil_k: http://bit.ly/1BJIkyS15:11
dhellmann41 of them, does that seem right?15:11
nikhil_kdhellmann: I was just checking the logs, seems right. We were working on stability and not features..15:12
dhellmannnikhil_k: great, it was a big number so I wanted to check first15:12
nikhil_kyeah :)15:12
dhellmannttx: I get an error from bash when I run milestone.sh. it might be that I have an older version on OS X? http://paste.openstack.org/show/316832/ I'll try to get the launchpad credentials to work from linux15:16
dhellmannttx: that part of the script works on linux; waiting to see if the launchpad login works15:19
ttxok, back15:20
ttxOlder versions of bash might not support ${PROJECT^}15:21
dhellmannyeah, I think that's the problem15:21
dhellmannugh, the launchpad thing is trying to auth me with lynx, which I'm pretty sure doesn't work15:21
ttxmight be simpler to tweak milestone.sh for OSX usage15:22
ttx${MILESTONE: -1} and ${PROJECT^} and ${BASH_SOURCE[0]} should be tested15:23
dhellmannhey, it seemed to work this time15:23
dhellmannmaybe last time I tried that I did something wrong, or maybe lynx has been upgraded15:23
ttxIf ${PROJECT^} is all that fails you should be able to run with ${PROJECT}15:23
dhellmannwhat does the ^ do?15:24
ttxcapitalize first letter15:24
ttxnova -> Nova15:24
dhellmannoh, ok15:24
ttxin the tag message15:24
dhellmannit's updating bugs now15:24
ttxso pretty invisible optimization anyway15:24
ttxwhich one are you running ? glance ?15:25
dhellmannglance has now15:25
dhellmannhmm, hit an error: http://paste.openstack.org/show/316835/15:25
dhellmann401 on a private bug it looks like15:26
ttxand with my legendary error recovery there we'll have to run the remaining parts of milestone.sh manually15:26
dhellmannI'm not seeing anything that tells me obviously what bug had the problem15:27
ttxI'll run it now15:28
ttxok it's just a handful of bugs that were left, let's see if any of those looks funny15:29
ttxI have access to security bugs which might be why I haven't hit that one yet15:30
ttxexcept none of the ones it listed for me are protected or anything15:31
ttxWe'll have to catch 401s and log them in process_bugs15:32
dhellmannttx: I need to run that errand. I'll check back in a bit and see what you learned.15:32
ttxcatches ServerError but 401 is probably 4xx15:32
dhellmannmakes sense; we could just catch all errors there15:33
ttxok, uploading now15:33
ttxnikhil_k: https://launchpad.net/glance/+milestone/liberty-1 completed15:34
*** mestery has joined #openstack-relmgr-office15:34
SlickNikHi ttx15:34
ttxSlickNik: hi!15:35
ttxShall we go through Trove and check the page is ready ?15:35
*** mestery_ has joined #openstack-relmgr-office15:35
nikhil_kttx: great. thanks.15:35
SlickNikSounds good— if you're not in the middle of something else.15:36
ttxSlickNik: script does not suggest any change15:36
ttxany feature missing from the list ?15:36
ttxif you have anything else significant we can retroactively create a BP for it15:37
SlickNikNo, we should be all good.15:37
ttxanything you would like to wait for before the tag ?15:37
*** mestery has quit IRC15:39
ttxmestery_: you have 5 min ?15:39
mestery_ttx: ack!15:39
* mestery_ secretly at DockerCon :)15:39
*** mestery_ is now known as mestery15:40
SlickNikttx: Don't need to wait for anything — should be all good to go.15:40
ttxThat's why you are mestery_. Running in a container15:40
ttxok tagging trove now15:40
ttxmestery: let's do a pass on https://launchpad.net/neutron/+milestone/liberty-115:40
ttxlet's see what my script suggests15:41
ttx(on the blurptins side)15:41
mesteryttx: Ack, waiting15:41
ttxSuggests targeting (implemented) https://blueprints.launchpad.net/neutron/+spec/ml2-dpdk-ovs-mechanism-driver15:42
mesterydoing it15:42
ttxwell the script will do it. It suggests to defer the 8 bps "needs code reveiw" too15:42
ttxshould we keep all of them on the track list at this point ? Could merge in the coming days ?15:43
mesteryack on that too15:43
ttxor should I just clean up15:43
mesteryWell, lets just clean up15:43
mesteryI expect IPAM may make it15:43
mesteryThe rest, not sure15:43
ttxalright, cleaning up15:43
mesterythank you!15:43
ttxon the bugs side, anythign you'd like to keep in the milestone ?15:43
* mestery looks quick15:44
ttxor can I just defer them all to l2 ?15:44
mesteryNone that stand out15:44
mesterydefer them all!15:44
ttxbug 1464363 is critical15:44
openstackbug 1464363 in neutron "Gate (gate-rally-dsvm-neutron-rally) broken" [Critical,In progress] https://launchpad.net/bugs/1464363 - Assigned to Chris St. Pierre (stpierre)15:44
mesteryWe are on that15:44
ttxbut that should not block liberty-1 ?15:44
mesteryarmax and kevinbenton have a strategy there15:44
mesteryarmax sent an email to the list on this one15:45
ttxok, deferring bugs15:45
ttxSo just let me know when you're ready to tag. Between now and Thursday15:46
ttxmestery: if you end up finishing a feature (or wanting to block on that merging) just add it back to l115:46
mesteryOK, lets target for tomorrow, I wanted to sync with kevinbenton and armax on a few things15:46
mesteryWill do, thanks ttx!15:46
mesterythank you!15:46
SlickNikttx: how to get involved with the libs release process?15:50
SlickNikttx: Figured I'd check because I noticed the clients moved to a release-lib process and figured that I should get involved helping with that since I'd like to do it for the trove client in any case.15:50
ttxSlickNik: the idea is to make all releases go through the same process -- currently it's pretty manual but we'll work on automating most of it15:51
ttxA bit busy to discuss that right now, maybe we should talk again when we are done with l115:51
SlickNikttx: sounds like a plan — will ask again at a more opportune moment. Thanks!15:52
nikhil_kttx: dhellmann : about project searchlight15:59
*** gordc has quit IRC16:00
nikhil_kwe believe that we won't go with l1 as things are getting setup16:00
ttxnikhil_k: right16:00
nikhil_kthere should be enough to release in l216:00
ttxwe'll see if we manage it directly or not by then16:00
nikhil_kttx: I didn't get you. Is there a separate process for managing it directly?16:01
ttxnikhil_k: some projects just push their own tags16:02
ttxespecially in the early stages when they can't or won't align with dev cycle milestones16:03
nikhil_kttx: makes sense16:03
nikhil_kttx: ah, does the re-centralization  affects this? or just libs and clients?16:03
ttxnot really. Rec-centralization is mostly about projects we were handling the main service releases of16:04
nikhil_kthanks ttx :)16:04
*** mestery has quit IRC16:28
*** dims has quit IRC16:30
*** dims has joined #openstack-relmgr-office16:33
*** AzherKhan has joined #openstack-relmgr-office16:51
dhellmannSlickNik: if you're interested in the library releases, you might be interested in reviewing https://review.openstack.org/19119316:52
dimsdhellmann: thanks for walking me through, i've released all the things :) now will wait for shoe(es) to drop16:56
dhellmanndims: cool, no issues with the tools?16:56
dimsdhellmann: worked like a charm16:57
dhellmanndims: wonderful! :-)16:57
dimsthe msmtp was just a bit tricky, other than that no issues16:57
dhellmannyeah, I had that set up already to work with sup so I just reused it16:58
SlickNikdhellmann: thanks! Taking a look at it.17:01
* dhellmann hangs up the office hour shingle a few minutes late17:03
dhellmanndavid-lyle: have a few minutes to chat about the milestone?17:05
david-lyledhellmann: sure17:05
dhellmanndavid-lyle: reviewing https://launchpad.net/horizon/+milestone/liberty-117:06
dhellmannI suspect most of those blueprints need to be retargeted to L2? unless you think some will close by thursday17:06
dhellmanndavid-lyle: here's the dry-run output from the update script: http://paste.openstack.org/show/317139/17:07
david-lylethey will move17:07
dhellmanndavid-lyle: ok, are any of those open bugs things we should make sure we wait for?17:07
david-lyledhellmann: no, we're in the midst of some refactoring that's blocking several other efforts. So that small list looks accurate17:08
dhellmanndavid-lyle: ok, so the scripts will retarget all of the open items when we run it. Are you ready to tag, or do you have something in process that you'd like to wait a bit for?17:09
david-lyleI'm ok with tagging now17:10
david-lylewell actually, let me check a gate  bug first17:10
dhellmanndavid-lyle: standing by17:10
dhellmanndavid-lyle: take your time17:10
david-lyleneed this https://review.openstack.org/#/c/194686/  to merge first17:11
david-lyleI'll ping you when I see it land17:11
dhellmanndavid-lyle: ok, sounds good17:11
dhellmanndavid-lyle: thank you!17:11
dhellmanndavid-lyle: I can go ahead and update everything else, if that's ok with you (leaving just bug 1467950 as an open bug in L1)17:12
openstackbug 1467950 in OpenStack Dashboard (Horizon) "test_floatingip and test_keypair tests are failing" [Critical,New] https://launchpad.net/bugs/146795017:12
david-lyledhellmann: that works for me17:14
dhellmanndavid-lyle: ok, starting that now17:15
*** AzherKhan has quit IRC17:16
dhellmanndavid-lyle: https://bugs.launchpad.net/horizon/+bug/1436903 is marked as critical, is that another gate bug?17:20
openstackLaunchpad bug 1436903 in OpenStack Dashboard (Horizon) "integration tests failing blocking gate" [Critical,Confirmed] - Assigned to David Lyle (david-lyle)17:20
*** AzherKhan has joined #openstack-relmgr-office17:20
dhellmannmorganfainberg: have time to chat about the milestone for keystone?17:22
david-lyledhellmann: they appear to be at least partially duplicates17:25
*** mestery has joined #openstack-relmgr-office17:25
david-lylethe patch going in is just to work around the issue for now17:25
dhellmanndavid-lyle: ok, shall I bring 1436903 back into the milestone, or leave it in L2?17:25
david-lyleleave, it in L-2, the proposed patch is just to skip the tests17:26
david-lylefor now17:26
david-lylewait nevermind, different issues17:27
david-lylebut the answers remain the same17:27
dhellmannok :-)17:27
david-lylejust need the one review to land17:27
dhellmanndavid-lyle: and that's a work-around for the bug? so it won't be closed by the patch landing?17:28
david-lylethat's correct, so we should move the first bug to L-2 as well17:28
david-lylethe patch won't close it17:28
dhellmanndavid-lyle: ok, I'll take care of that, thanks for clarifying17:28
david-lyleour integration test suite is fragile and fixes take some time17:29
dhellmannyep, I understand, I just want to make sure the milestone is accurate and we wait if you want something else to land, so no worries17:29
dhellmanndavid-lyle: you also have time to create blueprints for any major work that was done but for which there's no blueprint, yet, if you need to do that. Other than that, I think we're done with the review, so I'll wait for your go-ahead before tagging the milestone.17:33
dhellmannstevebaker: have a few minutes to chat about the milestone this week?17:39
dhellmannkiall: have a few minutes to chat about the milestone this week?17:44
morganfainbergdhellmann: sure17:51
dhellmannmorganfainberg: https://launchpad.net/keystone/+milestone/liberty-117:51
dhellmannmorganfainberg: this is the output from a dry-run of the blueprint update script: http://paste.openstack.org/show/317142/17:52
dhellmannare you comfortable with retargeting all of the incomplete blueprints to L2?17:52
* morganfainberg waits for paste to load17:52
morganfainbergdhellmann: a couple of them are complete17:52
dhellmannyeah, we seem to have a spam bot hammering the server or something17:52
morganfainberglet me update them in a sec17:52
*** bswartz has joined #openstack-relmgr-office17:53
morganfainbergdhellmann: ok updated17:55
morganfainbergbumped the bps that aren't doen to l2 and l317:55
dhellmannmorganfainberg: ok -- I have a script to retarget these things, so you just need to tell me which ones to ignore :-)17:55
dhellmannmorganfainberg: same question for the bugs, are any of those blocking L1 or can they all go to L2?17:56
morganfainberglooking at bugs now17:56
morganfainbergall bugs can be bumped17:57
morganfainbergthat aren't committed17:57
dhellmannmorganfainberg: do you have any work that isn't reflected in a blueprint that you'd like to make sure is highlighted?17:57
morganfainbergnot that i can think of17:58
morganfainberghmm. LP is timing out17:58
morganfainbergthe wont fix bug should be not assigned to *any* milestone17:58
dhellmannok, I'll see if the script can fix that17:58
morganfainbergdhellmann: i got it unassigned17:59
dhellmannmorganfainberg: ok, reload the milestone page and make sure that looks good to you, the script is done17:59
dhellmannok, are you ready for a tag today, or are there patches in the queue you'd like to wait for?18:00
morganfainberggo for it18:00
dhellmannok, tagging now18:00
morganfainbergthe only patches i would wait for are not critical and need to be respun, so holding off is silly18:00
morganfainbergif they were gating it would be a different story18:00
*** mestery has quit IRC18:00
dhellmanntag pushed, waiting for the tarball build to complete18:01
*** mestery has joined #openstack-relmgr-office18:01
dhellmannwell, the script broke again, so I'll need to do some more of this by hand18:02
dhellmannmorganfainberg: I think you're all set. I'll finish this work up but I shouldn't need you for that. Thanks!18:04
*** mestery has quit IRC18:10
bswartzdhellmann: are you doing all the release management for liberty or are you and ttx splitting the job?18:31
dhellmannbswartz: we're splitting it18:31
bswartzdhellmann: I'm trying to get the L-1 stuff on LP in shape18:32
bswartzwe have a few things still in flight so we're not ready for a tag today18:32
dhellmannbswartz: ok. The script we have will do some of that for you, so let's chat18:32
*** isviridov is now known as isviridov_away18:32
bswartzI'll see if I can get everything sorted out by tomorrow18:32
bswartzwell some BPs are in a questionable state -- I need to track down people to answer those questions18:33
dhellmannok, questions it can't answer :-)18:33
*** j^2 has joined #openstack-relmgr-office18:33
dhellmannit will however save you the trouble of retargeting bugs and blueprints yourself18:33
j^2hey all18:33
dhellmannhi, j^218:33
dhellmannbswartz: so, nail down the status of what you have there now, and then check back in here with ttx or me18:34
bswartzdhellmann: so what is the recommended approach for BPs which were targeted but NOT completed? leave them in a good progress/needs code review state and targeted at L-1?18:34
dhellmannbswartz: they'll either move to L2 or be untargeted completely, but the script can do that so you don't have to do it by hand18:35
dhellmannbswartz: when we're all done, we want the milestone to only have closed bps and bugs in it before we close it and tag the release18:35
bswartzbut I need to be involved with the decision to push to L2 or to retarget -- how is that decision made?18:35
dhellmannyou should also identify anything you have in flight that should hold up the milestone -- at this point it would have to be pretty critical18:35
dhellmannbswartz: oh, you just make it18:35
bswartzokay I'm more comfortable doing it myself rather than relying on the script18:36
dhellmannso you *could* update each one by hand if you want to push them to different places, but the script will move them all to L2 automatically for you if that's what you want18:36
dhellmannthat's fine then18:36
dhellmannget it into the state you're happy with, and then let us know when you're ready to tag the milestone18:37
lifelesssdague: thanks18:37
lifelesssdague: https://review.openstack.org/#/c/189250/ could use a +2 then18:38
*** openstackgerrit has quit IRC19:21
*** openstackgerrit has joined #openstack-relmgr-office19:22
dhellmannttx: would you look over http://paste.openstack.org/show/317317/  to make sure the work I finished by hand for keystone looks ok?19:30
ttxI'm on it19:30
ttxweird error you got there19:31
ttxlooks complete though19:31
dhellmannyeah, I didn't spend a lot of time debugging that one, it looked like some sort of connection/proxy/gateway issue19:31
ttxthat requests.get is pretty straightforward19:31
ttxwe might need to build some retries into that script19:32
dhellmannI made a note about looking into making the whole tool more idempotent, too19:32
ttxused to be much simpler, but now it's non-trivial to "finish" it19:33
ttxI'll ping stevebaker after thr cross-project meeting, maybe we'll hit the sweet spot then19:33
dhellmannttx: sounds good, I figured it was a tz issue there19:34
ttxSo who are we missing19:35
ttxstevebaker and Kiall ?19:35
dhellmannyes, I think that's it19:38
dhellmannI talked to bswartz but didn't tag manila, yet19:38
ttxok let's try to get to the last 2 after/during the meetings19:39
dhellmannsounds good19:40
*** Rockyg has joined #openstack-relmgr-office19:51
morganfainbergdhellmann: ok we need to rip out the requirements check still for middleware.20:08
morganfainbergdhellmann: i'll get that proposed (stable/kilo) i guess shortly20:08
morganfainbergdhellmann, ttx: hoping to have stevemar sub/proxy for me at x-project meeting20:09
morganfainbergas an FYi20:09
*** Rockyg has quit IRC20:40
*** Rockyg has joined #openstack-relmgr-office20:41
*** Rockyg has quit IRC20:47
*** Rockyg has joined #openstack-relmgr-office20:48
bswartzttx, dhellmann: manila is ready for tag after this change lands: https://review.openstack.org/#/c/177834/21:26
ttxbswartz: should we taregt the corresponding blueprint ?21:29
bswartzI think it is targeted and marked implemented (I just did it 2 minutes ago)21:29
ttxoh, it's there already21:29
ttxLet's mark it Needs Code review while this merges21:30
ttxbah, in the pipe21:30
ttxlet's just kep a tab open21:30
bswartzyeah it should be done in no time21:30
ttxbswartz: thx!21:31
ttxKiall: around?21:33
ttxstevebaker: around?21:34
stevebakerttx: hi21:34
bswartzttx: gah the gate job failed21:34
bswartzprobably random but a recheck will be needed21:34
ttxstevebaker: would you have time now for cleaning up the milestone page before we push the liberty-1 tag ?21:35
ttxBAsically deferring from https://launchpad.net/heat/+milestone/liberty-1 what won't make it21:36
stevebakerttx: I'm doing that now. There are a handful of bps which will need to wait about 2 hours for asalkeld to wake up so I can get updates on them, then heat l-1 will be ready21:36
bswartzttx: what's the command to restart the gate jobs but not the check jobs?21:37
ttxstevebaker: my script suggests adding https://blueprints.launchpad.net/heat/+spec/no-downward-sql-migrations which was completed recently21:38
ttxand https://blueprints.launchpad.net/heat/+spec/support-actions-for-remote-stack21:38
ttxand https://blueprints.launchpad.net/heat/+spec/volume-backup-resource21:38
ttxand https://blueprints.launchpad.net/heat/+spec/mistral-resources-for-heat21:39
ttxI can do it if you confirm that those were done between kilo FF and l121:40
stevebakersure, going through them now21:40
stevebakerthis is looking like our biggest *-1 ever21:40
ttxI have a script to defer all l-1 targeted bugs that are not fixcommitted yet to l-221:40
ttxlet me know if there is anything there you'd liek to keep in the milstoje as a tag blocker21:41
ttxtyping too fast at this late hour21:41
stevebakerok, I'm not seeing any blockers yet21:41
ttxok, moving them then21:41
stevebakerttx: I'm just going through them now to see if any are ready to approve21:42
ttxstevebaker: OK, you should keep any of those last three open blueprints that may still make it in the coming day21:43
ttxand defer / untarget the other(s)21:43
ttxtaht way we know what do wait on before tagging21:44
ttxwhat to wait on I mean21:44
stevebakerttx: they are either in already or can be deferred, but the changes are a bit of a tangle so it is not obvious to me if they're done. I'll ask asalkeld when he is up21:44
ttxOK, just let us know if it's ready to tag by the end of your day21:44
stevebakersure, will do21:45
ttxyou can ping me or dhellmann here21:45
ttxhave a good day!21:45
stevebakerttx: thanks, good evening21:45
ttxKiall: if you ever show up you can try toi ping dhellmann. Otherwise ping us tomorrow21:47
* dhellmann expects to be going offline in not too long21:49
david-lyledhellmann: https://review.openstack.org/#/c/194686/ merged, feel free to tag horizon as per your convenience, thanks21:50
dhellmanndavid-lyle: ack21:50
ttxdhellmann: going to bed now22:03
ttxfeel free to be adventurous, it's only liberty-1 :)22:03
* ttx disappears22:04
dhellmannttx: I'm tagging horizon now -- lots of bugs to update22:04
dhellmanndavid-lyle: horizon L1 is done, tagged as
david-lylethanks dhellmann22:05
*** Rockyg has quit IRC22:08
lifelessbswartz: recheck22:26
lifelessbswartz: (AFAIK there is no 'gate jobs only' recheck mode)22:27
morganfainbergdhellmann: https://review.openstack.org/#/c/194849/ the removal of the requirements job for stable/kilo of keystonemiddlewate22:42
dhellmannmorganfainberg: +122:44
morganfainbergdhellmann: makes me sad we have to do that though :(22:44
dhellmannmorganfainberg: yeah, we'll do better for liberty22:44
openstackgerritJoshua Harlow proposed openstack-infra/release-tools: Optional include pypi package url link in release notes  https://review.openstack.org/19485022:44
morganfainbergdhellmann: almost hard not to.22:44
dhellmannmorganfainberg: yeah, well, it turns out to be sort of complicated to sync requirements changes into repos when some of them are the libraries that are getting the requirements changes...22:45
morganfainbergdhellmann: well also doing it as an after-the-fact-thing is unfun22:46
bswartzlifeless: is there any difference at all between recheck and reverify?22:48
lifelessbswartz: there was in the dawn of time22:48
lifelessdhellmann: soooo if I can borrow your +222:51
lifelessdhellmann: https://review.openstack.org/#/c/189251/ is entirely mechanical (I ran the script, captured the output) - and is green [the failure was in a neutron test, unrelated]22:52
dhellmannlifeless: +222:52
dhellmannlifeless: where did we end up on the changes to the way version ranges are expressed elsewhere?22:53
lifelessI'm going to discuss it upstream22:53
lifelessin packaging22:53
lifelessits not critical path IMO22:53
lifelesswe didn't have a standard before22:53
lifeless[if we did, we'd have had a linter]22:53
lifelessI'm happy to add one22:53
dhellmannok, I don't have a strong opinion I was just curious22:54
lifelessdhellmann: I think you'll like https://review.openstack.org/#/c/194349/22:54
lifelessthere was a weak variation landed overnight, but my fix is better as it reports all the issues22:54
lifelesshttps://review.openstack.org/#/c/194350/ makes requirements itself able to be update.py synced22:55
lifelessand https://review.openstack.org/#/c/194351/ is the result of running update.py to sync it22:55
dhellmannall of that LGTM22:56
lifelessnow to find a second22:56
*** dims has quit IRC23:56

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