Wednesday, 2015-04-22

*** david-lyle has quit IRC00:24
*** david-lyle has joined #openstack-relmgr-office00:27
*** asalkeld has joined #openstack-relmgr-office04:03
*** asalkeld has quit IRC06:37
*** asalkeld has joined #openstack-relmgr-office06:37
*** asalkeld has quit IRC06:37
*** asalkeld has joined #openstack-relmgr-office06:38
*** zz_johnthetubagu is now known as johnthetubaguy08:55
*** asalkeld has left #openstack-relmgr-office10:29
ttxdhellmann: could you review https://review.openstack.org/#/c/175851/ ? We'd like that one in before we sync the fix12:51
dhellmannttx: that's a lot of reverts12:52
ttxthe more the merrier12:52
dhellmannthis patch is restoring the new behavior, again, right? I thought we decided this optimization might be at fault?12:52
ttxI'll admit I didn't follow the logic there. Ask jd ?12:55
dhellmannI've asked him to join us here, but haven't seen a response yet12:55
ttxI can only split my attentin into so many threads12:55
dhellmannyeah12:55
dhellmannthat's why I asked jd to lead on this one; but I'd like to understand what's going on before approving this -- it looks fine, except the 3 "revert"s in the commit message12:56
ttxhopefully it's not not not not fixing it12:58
sdaguettx: keystone is the primary effected project, however we have no test results with keystone with this patch yet13:01
sdagueit would be good to get those results13:01
sdaguedhellmann: no, this patch is reverting all the optimizations13:02
sdaguethe optimization was added, reverted, readded13:02
sdaguethis would double revert it13:02
dhellmannsdague: I'm confused, because I thought the optimization was introducing the greenthread.sleep call and that seems to be coming back in this diff. I didn't get a lot of sleep last night, though, so I could be reading https://review.openstack.org/#/c/175851/1/openstack/common/service.py,cm wrong13:05
sdaguedhellmann: no, that's the juno code in there again13:09
dhellmannah, no, the optimization is actually removing that call13:09
sdagueyep13:09
dhellmannETOOMANYREVERTS13:09
dhellmannttx: +2a on https://review.openstack.org/#/c/17585113:10
sdagueok, so then can someone the minimal fix onto stable/kilo keystone?13:11
sdaguethen I can setup a test13:11
dhellmannI'll set that up13:11
dhellmannthe sync to keystone that is13:11
sdaguedhellmann: thanks13:13
SergeyLukjanovdhellmann, hi, I have a question re sahara client release13:20
dhellmannhi, SergeyLukjanov13:22
SergeyLukjanovdhellmann, I'm a bit surprised that you pushed new tag yesterday :)13:22
dhellmannSergeyLukjanov: yes, we needed to release libraries to let us uncap requirements for liberty13:23
SergeyLukjanovdhellmann, is it single time done or you'll release clients always?13:23
dhellmannSergeyLukjanov: just this once, I hope :-)13:23
SergeyLukjanovdhellmann, okay, got it :)13:23
dhellmannSergeyLukjanov: my goal is to make sure there are enough good tools in place that I don't have to actually do any work ;-)13:24
ttxsdague: I could recheck a keystone stable/kilo thing and make it depending on that fix ?13:24
SergeyLukjanovdhellmann, I've been really surprised today's morning when I've been unable to create 0.9.0 tag and enough sleepy to miss that it was created by you :)13:24
SergeyLukjanovdhellmann, (/me even reinstalled git, hm...)13:24
dhellmannSergeyLukjanov: lol, sorry about that!13:25
SergeyLukjanovdhellmann, that's ok, just funny ;)13:25
ttxok, looks like the world is partially unbroken now, I'll get a few RC2 fixes in while it holds13:25
SergeyLukjanovdhellmann, ttx, when should I release minor client in stable/kilo to have latest requirements in it? next week?13:26
dhellmannttx: I'm testing the keystone change locally a bit before I submit it because I ended up editing the result of the sync to remove some unrelated stuff13:26
dhellmannSergeyLukjanov: please don't release anything else until we're all clear on the RC2 versions13:26
dhellmannnext week at the earliest, but ttx will give notice that it's ok to do13:26
SergeyLukjanovdhellmann, sure, I understand :) that's why I'm asking, so, waiting for ping :)13:27
sdaguettx: I need to set up a specific depends on13:27
sdaguedhellmann: where is the review for the keystone thing?13:28
dhellmannsdague: running unit tests locally13:28
sdaguedhellmann: ok, thanks, just give me a heads up once it's up. Stepping away for a minute.13:29
dhellmannsdague: sure13:29
ttxdhellmann: so next thaw steps would be... https://review.openstack.org/#/c/176036/ (9.7) and allowing the late stable/kilo libs (13.)13:29
ttxdhellmann: do you think we can proceed with that ? Shall we wait and merge a few other RC2 things before risking to break the world again ?13:30
dhellmannsdague: https://review.openstack.org/17630613:31
dhellmannttx: checking...13:32
dhellmannttx: yes, let's restore the requirements check jobs for libraries (9.7)13:33
dhellmannttx: I would prefer to hold off on more library releases until we're sure stable/kilo is actually running smoothly13:34
dhellmann(13)13:34
ttxfungi: maybe it's time for https://review.openstack.org/#/c/176036/13:35
ttxdhellmann: ok, one step at a time13:35
dhellmannttx: right13:35
sdagueok https://review.openstack.org/#/c/175391/ is the test13:35
sdagueI'm going to be unavailable for much of the day starting in about an hour, so it would be worth seeing https://review.openstack.org/#/c/175391/ pass it's grenade tests a couple of times to know that this fixed the keystone issue13:37
fungiso do we want to press forward readding requirements check jobs to master, or is there a chance we still need them suspended to un-wedge things needed for the kilo release now?13:37
dhellmannfungi: hmm, good point. we needed that to allow releases for libs that had no caps, which we now have. ttx: did we land the g-r update to master without the caps, too?13:38
ttxfungi: that is a good point I guess. This chnage does not make us closer to kilo13:39
ttxThat would be https://review.openstack.org/#/c/173924/13:39
dhellmannyeah, let's get that in first13:39
ttxworth a recheck I guess13:39
dhellmannI'll do that unless you've beat me to it13:40
ttxdid it13:40
dhellmannheh13:40
ttxNext on the critical path is the ability to do new lib releases on stable/kilo13:40
ttxwhich is in theory fixed by the recent release of liberty versions13:40
ttxbut we may want to hold a little more to be sure stable/kilo is relatively in good shape first13:41
ttxand land a few RC2 fixes13:41
ttxlike, say, the swift ones13:41
dhellmannyes, I agree13:41
dhellmannshould we update the order of the steps in the etherpad?13:41
ttxgate is definitely looking greener13:41
ttxwe need a mind-maps etherpad13:42
sdagueso, I would hold on any further unfreeze bits until https://review.openstack.org/#/c/175391/ lands, because right now the system is upgrading from stable/juno -> liberty13:44
dhellmannttx: http://www.mindmup.com13:45
ttxdhellmann: oooh13:45
sdagueand the double jump with all the currently narrow requirements is way more risky than if it's single release hops13:45
ttxsdague: ok13:46
ttxso we should add that to the big-thaw etherpad13:47
dhellmannttx, sdague : I don't see a cross-project session to talk about requirements. do we want one there, or in the release track?13:48
ttxI think a fishbowl is the wrong way to talk about it13:49
ttxdon't want to expose the problem space again13:49
ttxI want to work on a solution :)13:49
ttxso I want to dedicate part of the QA/Infra/Relmgt meetup to disucss it13:49
ttx(on Friday)13:50
dhellmannok, makes sense13:50
dhellmannI'm going to reorder some of the steps based on what we've talked about just now13:50
ttxin the fishbowl we end up introducing the issue again and again and feel the whole hour with "we tried that and it failed"13:50
sdagueso, if it's during the meetup, I will probably not be there, because Nova conflicting bits13:50
sdaguehonestly, I really think this feels more like a sprint13:50
ttxsdague: Nova conflicts with everything13:50
sdagueyep13:51
ttxall days13:51
ttxso Friday or not Friday is a bit of the same :)13:51
dhellmannsdague: a sprint does sound right, but I'd like to at least have a plan for making a plan for that sprint13:51
dhellmannttx: please check the new order for 9.7-9.1013:52
ttxweird, a pep8 fail in the gate pipe13:52
sdaguettx: the difference with Friday is the unstructured time is more nebulous about what's missable13:52
dhellmannyeah, it would be good to have some time blocked out for this13:53
*** sileht has joined #openstack-relmgr-office13:53
ttxwe could use a RelMgt or QA or Infra workroom13:53
sdagueI really think this is going to require 2 to 3 days to architect the solution13:53
dhellmannsdague: so a separate meetup, or online?13:53
sdagueseparate meetup, however, at minimum jeblair should be in this planning conversation, so this is probably the wrong room for it.13:54
dhellmannttx: that pep8 failure looks legit, but it is weird to see it in the gate13:54
dhellmannsdague: yeah13:54
sdaguedhellmann: it's not that weird, that patch last had tests run on it on March 1213:55
sdaguehttps://review.openstack.org/#/c/87869/13:55
ttxhah! fun13:55
dhellmannah, I didn't look that deeply13:55
sdagueif you look that deeply you get ragey about core reviewers and want to start kicking out a lot of projects ....13:56
sdaguebecause people do stuff like that *a lot*13:56
*** johnthetubaguy is now known as zz_johnthetubagu13:57
ttxdavid-lyle, devananda: ping me when around to discuss opportunity of opening RC2 for you14:49
dhellmannttx: It looks like the fix in keystone is helping with https://review.openstack.org/175391 so far. I'm going to run an errand for a bit.14:55
ttxack14:56
*** russellb has quit IRC15:00
*** zz_johnthetubagu is now known as johnthetubaguy15:03
*** johnthetubaguy is now known as zz_johnthetubagu15:03
*** zz_johnthetubagu is now known as johnthetubaguy15:04
*** russellb has joined #openstack-relmgr-office15:05
devanandattx: g'morning15:08
ttxdevananda: ohai15:08
ttxdevananda: so... ironic RC215:09
devanandattx: two fixes landed on master, nothing else targeted for rc2 as of last night15:09
* devananda sips his coffee and looks at LP15:09
ttxdevananda: ok, so we could open RC2 and target those two backports to it15:09
ttxdevananda: does that make sense ?15:09
devanandacombing the bug list and poking people (because, yes, they need extra poking today)15:13
devanandaI think we found 1 more, already fixed in master, to backport15:13
ttxok add it to kilo-rc-poten,tial list and I'll copy it over15:15
ttxcreating RC215:15
ttx(milestone in LP, not tag)15:15
ttxchecking the patches...15:17
ttxhttps://launchpad.net/ironic/+milestone/kilo-rc215:18
devanandattx: thanks15:19
ttxhttps://review.openstack.org/#/c/171544/ will need a backport15:19
devanandaalso, not sure if I did something wrong previously, but that bug is marked as fix-committed, yet the commit seems to already be on stable/kilo15:20
devanandashouldn't it be fix-released?15:20
ttxfor which ?15:20
* devananda clearly needs more coffee for brains to function15:20
devanandahttps://bugs.launchpad.net/ironic/+bug/144101415:20
openstackLaunchpad bug 1441014 in Ironic kilo "Improper error handling when Ironic application runs under Apache2" [High,New]15:20
devanandahttps://review.openstack.org/#/c/171544/115:21
ttxit's not in stable-kilo is it ?15:21
ttxah hm15:21
ttxprobably was at the wrong state15:22
ttxand didn't get picked up15:22
ttxgot merged before we actually cut the branch15:22
devanandait is15:22
devanandayea... huh15:22
ttxweird15:22
ttxI'll fix15:22
devanandathanks15:23
ttxok done, marked released in RC115:24
devanandacheers. that was strange15:24
ttxSo we are back at 2 fixes15:24
devanandayep. shall we +A them?15:24
ttxI can handle that15:24
devanandaneat15:25
ttxwon't be able to tag the RC2 until we get requirements in anyway15:25
ttxso no hurry as long as you're not too far behind15:25
ttxdevananda: thx. Let me know if anything else appears on your radar15:26
devanandai'll keep an eye out for requirementsbot - shall I approve those, if/when they come in?15:26
devanandaactually, there's one up now15:27
devananda17432715:27
ttxdevananda: n opoint, it will be refreshed once we do the libs update15:29
devanandak15:29
ttxdhellmann: should we keep https://review.openstack.org/#/c/175859/ or https://review.openstack.org/#/c/176306/ ?15:30
ttxI would say we keep the one that spells Depends-On correctly15:30
ttxalthough Julien's was also proposed to master.15:33
devanandattx: one more patch for kilo: https://review.openstack.org/#/q/status:open+project:openstack/ironic+branch:stable/kilo+topic:translations,n,z15:41
ttxthingee: unclear if https://review.openstack.org/#/c/175740/ should be approved, jgriffith posted a number of - comments15:42
ttxdevananda: I'll merge that one last, may be refreshed15:42
devanandak15:42
ttxnotmyname: unclear if I should approve https://review.openstack.org/#/c/176110/ -- clay seems opposed to it15:43
notmynamettx: yeah, I was looking at that this morning. haven't talked to clayg yet15:44
jgriffithttx: I'm defering to thingee seems he wants it, but I wanted to communicate with him what i thought was wrong.15:44
jgriffithttx: he can weigh it out and use his judgement, I patched the root bug... good enough for me15:44
notmynamettx: it won't land with his -2 on it, so we need to hold off on that for a bit15:44
ttxnotmyname: sure15:45
ttxdhellmann: err.. so jd__ approved https://review.openstack.org/#/c/173924/ (the liberty uncap) -- I guess that's part of the "bring fun back to openstack" platform15:53
dhellmannttx: if julien's patch was also submitted against master we should use that, but sdague's test patch was marked as depending on mine https://review.openstack.org/#/c/175391/15:53
dhellmannttx: we should probably go through and -2 anything we've submitted that we need to land in order15:53
ttxdhellmann: hmm15:54
dhellmannI forgot julien had submitted that fix to keystone already when I redid it15:55
ttxDo we really want https://review.openstack.org/#/c/175391/ before https://review.openstack.org/173924 though ?15:55
dhellmannI'll abandon my patch and update the other commit message15:55
thingeettx, jgriffith I'm fine with a -2 on the backports if we're concerned with regression15:55
thingeeI can see that15:55
ttxthingee: I'd rather keep risky patches out, yes15:55
ttxI'll let you un-RC2 it15:55
thingeek15:55
jgriffiththingee: ttx thanks15:56
ttxdhellmann: saw you k-lined it. ack15:56
dhellmannttx: at least to give us time to think, I just sat back down15:57
*** patchbot has joined #openstack-relmgr-office15:57
notmynamettx: I agree with clayg on patch 176110 and have talked to another core about it. it should NOT be in RC2. any issues there should be handled later, if they exist15:57
patchbotnotmyname: https://review.openstack.org/#/c/176110/15:57
notmynamettx: and I've retargeted that bug away form rc215:58
ttxnotmyname: ok15:58
dhellmannttx: sdague's patch to add stable/kilo support to d-g (https://review.openstack.org/#/c/175391/) now depends on julien's patch for the service module in keystone (https://review.openstack.org/#/c/175859/)16:00
ttxdhellmann: not sure that's a good idea, since the patch is likely faulty16:02
ttxdhellmann: see discussion in #-oslo16:02
dhellmannttx: ok, it was depending on my version of the same patch before, so this move was to clear up the confusion from having the duplicate16:04
ttxdhellmann: bknudson proposed https://review.openstack.org/#/c/176151/ instead16:08
dhellmannttx: I wish we had an owner for this code. :-/16:09
ttxdavid-lyle: around?16:13
david-lylettx: o/16:35
*** russellb has quit IRC17:17
*** russellb has joined #openstack-relmgr-office17:21
-openstackstatus- NOTICE: gerrit is restarting to clear hung stream-events tasks. any review events between 16:48 and 17:32 utc will need to be rechecked or have their approval votes reapplied to trigger testing in zuul17:33
*** russellb has quit IRC17:35
*** russellb has joined #openstack-relmgr-office17:40
*** david-lyle has quit IRC17:42
*** david-lyle has joined #openstack-relmgr-office18:07
*** johnthetubaguy is now known as zz_johnthetubagu18:07
ttxdavid-lyle: o/18:35
david-lylettx: o/18:36
ttxdavid-lyle: yesterday we said we might want to open RC2 today18:36
ttxlooking into your bug list18:36
ttxhttps://bugs.launchpad.net/horizon/+bugs?field.tag=kilo-rc-potential18:36
ttxhmm, not so much more in18:36
david-lyleindeed18:37
ttxdavid-lyle: anything you'd want a RC2 for ?18:37
david-lylewe need it for final translations18:37
david-lyleETA tomorrow18:38
ttxOK, let's include the two fixcommitted bugs there18:38
david-lyleok18:38
ttxand open it now so we can pick up translations tomorrow18:38
david-lyleI think backports are already proposed18:38
ttxlet me see18:38
david-lyleamotoki will work on translation commit18:38
david-lylethat one's more complicated18:38
ttxhttps://launchpad.net/horizon/+milestone/kilo-rc218:40
ttx+ the translatiosn obviously18:40
david-lyleactually a couple more that aren't tagged properly18:40
david-lylehttps://review.openstack.org/#/q/project:+openstack/horizon+branch:+stable/kilo,n,z18:41
david-lyleI will update the tags18:41
ttxShall we include that one ? https://bugs.launchpad.net/horizon/+bug/144234118:41
openstackLaunchpad bug 1442341 in OpenStack Dashboard (Horizon) "Admin Network panel Status isn't translatable" [Medium,Fix committed] - Assigned to Doug Fish (drfish)18:41
ttxand this one ? https://bugs.launchpad.net/horizon/+bug/144413518:41
openstackLaunchpad bug 1444135 in OpenStack Dashboard (Horizon) "csv file has concatenation" [Low,Fix committed] - Assigned to Doug Fish (drfish)18:41
ttxthat's the two additional proposed backports18:42
ttxif yes, let's add them directly, no need to tag18:42
david-lylesecond one certainly18:42
ttxdavid-lyle: you should also chase down lin-hua cheng so that he removes his -2 on https://review.openstack.org/#/c/175869/18:43
ttxok, adding second one18:43
david-lyleI need to check the first to make sure the .po will map properly18:43
david-lyleand yes I'll get lhcheng to remove -218:43
david-lylehe's just waiting on RC-218:44
ttxok let's keep the first on the potential list18:44
david-lyleok, will track that down18:45
ttxsounds good, will get a few merged in the mean time18:45
david-lylesounds good18:45
david-lylethanks!18:46
ttxdavid-lyle: wait18:46
david-lyleuh oh18:46
david-lyle:)18:46
ttxhttps://review.openstack.org/#/c/176031/ comment says it changes strings as well18:46
ttxshoudl I proceed and approve it, or would you rather pause18:47
david-lylelooking more closely, it doesn't seem worth it for Kilo18:48
david-lyleI'm pretty sure the translation will be broken18:48
ttxok, let's remove the target then18:48
david-lyleyes18:48
ttxcan you leave a -2 on it ?18:48
david-lylesure18:49
david-lyledone18:50
ttxthx!18:50
david-lylegood catch18:50
notmynamettx: SHA for RC2 has landed, team meeting starting in 5 minutes. will confirm that we've got a good RC2 and let you know18:55
ttxnotmyname: ok, I'll be around18:57
ttxnikhil_k: around ? You guys really need to get fixes merged in master if you want them in a RC219:06
ttxnikhil_k: can't wait a lot more19:06
ttxSlickNik: ping19:07
*** david-lyle has quit IRC19:18
sdaguettx: hey, back now for a bit. What's the story on the keystone patch?19:25
morganfainbergsdague, i think we have it all spiun up and proposed. we were waiting for zuul to chew on the depends-on chain19:25
morganfainberghttps://review.openstack.org/#/c/176392/19:26
ttxsdague: apparently the original revert was not really changing anything, according to bknudson. Came up with a new patch19:26
morganfainbergttx, ah that part19:26
ttxI think sdague was still on that episode yes19:27
* morganfainberg goes and gets coffee and food cause... it's that time.19:27
morganfainbergor well long past that time19:27
sdagueok, do we have a more narrow test case sorted out?19:29
ttxsdague: no idea, I'll admit not having looked into that more. Was discussed on #-oslo though19:31
ttxdhellmann: sdague: if we still don't feel confident doing the last-minute library stable/kilo releases tomorrow, I think we should opt them to not trigger any requirements bump, so that we can cut RC2s with "correct" requirements in them19:32
ttxso that the libs are no longer on the critical path to RC219:32
sdagueso, I have to say, after digging out of that wedge yesterday, I'm no longer sure what "correct" is here19:33
ttxsdague: shall we move on #-oslo and pick up bknudson there ?19:33
sdaguesure19:33
ttxoh, you are already19:33
*** david-lyle has joined #openstack-relmgr-office19:41
ttxhmm, in fact that won't really change a lot of things, we still need requirements sync jobs up19:43
nikhil_kttx: sure, though I thought we wanted to sync tomorrow on that status. But thanks for reminding if we need them fixed19:47
ttxnikhil_k: yes, tomorrow is ok to open the RC2, but I'm a bit afraid of seeing that there is no progress on those patches19:51
ttxsince they will have to be merged to be considered and tomorrow is a bit of a last-chance19:51
nikhil_kttx: ok19:51
* ttx doesn't want to work all evenings next week too19:51
nikhil_kthanks for the pointer19:51
nikhil_k:)19:51
nikhil_ksorry about that19:52
*** asalkeld has joined #openstack-relmgr-office19:52
ttxthingee: added https://bugs.launchpad.net/cinder/+bug/1446583 to RC2, please review the master fix asap20:05
openstackLaunchpad bug 1446583 in Keystone kilo "services no longer reliably stop in stable/kilo" [Critical,In progress] - Assigned to Brant Knudson (blk-u)20:05
ttxyou can ping people in #openstack-oslo if you need details20:05
nikhil_kttx: I fixed some and some others are currently being looked over20:06
ttxdhellmann: about to call it a day, have a minute to discuss status ,20:06
ttx?20:06
dhellmannttx: yes20:07
ttxdhellmann: ok, so as far as release goes, we have a number of RC2 windows opened20:07
ttxWe'd like to close them once the right requirements can be merged into them, so that we don't need a RC3 for that20:07
dhellmannok20:07
ttxThat means reenabling the requirements sync job20:07
ttxand landing the last requirements bumps20:08
ttxOn the former...20:08
ttxWe prefer to land https://review.openstack.org/#/c/175391/ before we go there20:08
dhellmannok, I see a note about that in the-big-thaw20:09
ttxOn the latter...20:09
ttxOnly glanceclient is advocationg for a min-version bump after its library release20:09
dhellmannthey want that in master?20:10
ttxno, stable/kilo20:10
ttxBut then I guess if we completed the former we can do the latter20:10
* dhellmann hangs head20:10
dhellmannI guess kilo isn't "done" so we can bump the minimum20:10
dhellmannoh, that does look serious, ok20:11
ttxstable/kilo has python-glanceclient>=0.15.0,<0.18.020:11
ttxthey want 0.15.120:11
ttxso we'd release that20:11
dhellmannnot 0.17.1 as it says in the etherpad?20:11
ttxand set python-glanceclient>=0.17.1,<0.18.020:11
ttxerr, yes 0.17.1 sorry20:11
dhellmannok, just checking20:11
sdaguewhy do they want that?20:11
ttxthan sync that to... ceilometer cinder heat horizon ironic nova20:12
david-lylettx: we're good on https://review.openstack.org/#/c/175038/ for RC-220:12
ttxapparently 0.17.0 breaks nova completely20:12
ttxhttps://bugs.launchpad.net/python-glanceclient/+bug/144266420:12
openstackLaunchpad bug 1442664 in python-glanceclient "Since 0.16.1 client breaks nova when using https" [Critical,Fix committed] - Assigned to Stuart McLaren (stuart-mclaren)20:12
dhellmannttx: we could also do !=0.17.0 if earlier versions work20:12
ttxwell 0.16.1-0.17.0 breaks nova20:12
dhellmannah, ok20:12
dhellmannso yeah, let's keep it simple20:12
sdaguettx: tls only20:13
ttxsdague: I agree we could spare the sync20:13
ttxerr20:13
ttxwe could spare the min version bump20:13
ttxbut we still have to sync the requirements back into projects before RC2 anyway20:13
ttxso we still need to complete step 9 from https://etherpad.openstack.org/p/the-big-thaw20:14
ttxwhich we agreed to hold until https://review.openstack.org/#/c/175391/  lands20:15
ttxwhich is therefore on the critical path to RC220:15
SlickNikttx: o/20:16
ttxSlickNik: hey20:16
ttxStill nothing to backport on Trove ?20:16
SlickNikhi20:16
dhellmannttx, sdague : is the only thing holding up 175391 the sync of the service module changes into keystone?20:16
SlickNikWe've got one fix that we'd like to backport.20:16
ttxSlickNik: ok, let me open a RC2 milestone for that. Bug number ?20:17
SlickNikttx: https://review.openstack.org/#/c/176223/20:17
SlickNikbug 144673520:17
openstackbug 1446735 in Trove "MongoDB guest won't start" [High,Fix committed] https://launchpad.net/bugs/1446735 - Assigned to Doug Shelley (0-doug)20:17
sdaguethere is a grenade change it's sitting on top of that I need to either disconnect it from or land and cleanup after20:17
dhellmannsdague: I noted that in 9.7.2 in the-big-thaw so we can track it20:18
ttxSlickNik: ok, you got it -- anything else ? https://bugs.launchpad.net/trove/+milestone/kilo-rc220:18
dhellmannsdague: does https://review.openstack.org/#/c/175391/ actually depend on that grenade change, or was it just tied there for testing?20:19
SlickNikttx: No, that's it from a bug perspective — did we want to take a translations update with that?20:19
ttxSlickNik: we will. Waiting for AJaeger to potentially update it tomorrow20:20
ttxjust let me know if anything else shows up, other wise will tage tomorrow/friday20:20
ttxSlickNik: thx!20:21
SlickNikttx: sounds good. That fix is ready to merge — when's a good time to do that?20:22
ttxSlickNik: I just approved it20:22
sdaguedhellmann: it was there for debugging the failures20:22
SlickNikttx: sounds good. Thanks!20:23
dhellmannsdague: ok, I'm trying to make the list of steps of things to land, so do we want that or can we decouple it?20:23
sdagueyeh, let me get opinion from the dtroyer and jogo20:24
dhellmannk20:24
ttxdhellmann: do you think we need to do 9.8 before 9.9 and 9.1O ?20:25
dhellmannttx: I was just looking at that. I feel like we should restore the check jobs before we uncap the requirements20:25
dhellmann9.9, 9.10, 9.820:26
dhellmannthis is the section we just reordered earlier today, though...20:26
ttxargh, too late to hold everything in my head20:27
ttxif we do reenable the syncs before removing the caps... that means we may sync the caps in master20:27
ttxare they already ?20:27
* ttx is lost20:27
dhellmannoh, right, master is capped right now20:27
dhellmannso, you're right, we do want to remove the caps, then enable checks, then enable syncs20:28
* dhellmann goes to write that down20:28
ttxyou could reenable the syncs for stable/kilo20:28
ttxhmm, not sure we have that level of granularity20:29
ttxWe could also manually sync the reqs for stable/kilo20:29
dhellmannI thought all of this was still enabled for stable/kilo20:30
ttxTrying to make sure we don't rush anything to satisfy rc220:30
dhellmannsee my notes under the new 9.8 heading20:30
ttxdhellmann: is it ? hmm20:30
dhellmannttx: https://review.openstack.org/#/c/176036/2/zuul/layout.yaml,cm reverts a change that was only applied to master20:31
dhellmannto restore the check jobs20:31
ttxthat is separate from the sync bot though20:31
dhellmannand https://review.openstack.org/#/c/174447/ is changing the project list in master only20:31
ttxthe sync bot was disabled by https://review.openstack.org/#/c/174383/20:31
ttxhmm20:32
ttxchecking20:32
dhellmannmy copy of stable/kilo projects.txt includes some libs20:32
dhellmannall of oslo, based on a quick scan20:32
dhellmannwe only needed the requirements stuff fiddled in master, so I think we only did it there20:33
dhellmannttx: I'm pretty comfortable with the order of steps we have in 9.7-9.8.4 now20:34
ttxdhellmann: so.. the only change we pushed to stable/kilo reqs was this:20:34
ttxhttps://review.openstack.org/#/c/174171/20:34
ttxand it didn't trigger any sync to swift20:34
dhellmannok20:34
ttxhmm, though they synced it manually20:35
ttxso they may have beaten the bot20:35
dhellmannyeah20:35
ttxhhhhm20:35
ttxchecking one thing20:36
ttxOK, so I should probably approve requirements bumps in stable/kilo for projects now20:37
ttxrather than wait on a potential last minute req bump20:38
ttxdhellmann: can't prove you wrong, so you're most certainly right :)20:38
dhellmannthe only pending requirements change I see is for glanceclient: https://review.openstack.org/#/q/project:openstack/requirements+is:open+branch:stable/kilo,n,z20:39
ttxyes, the one sdague questioned above20:39
ttxok, let me approve the requirements syncs as they stand20:40
dhellmannah, the syncs20:40
ttx(for the RC2 projects)20:40
sdaguedhellmann: ok, we're going to land the debugging patch on grenade20:40
sdagueand it's +Aed20:40
dhellmannsdague: ok20:40
sdagueI had to update the commit message, so https://review.openstack.org/#/c/175391/ is back in check for new tests20:40
sdaguethat needs infra folks to review20:41
dhellmannttx: you're looking at this list? https://review.openstack.org/#/q/owner:%22OpenStack+Proposal+Bot%22+status:open+branch:stable/kilo,n,z20:41
ttxhttps://review.openstack.org/#/q/branch:stable/kilo+topic:openstack/requirements,n,z20:41
ttxshould not be very different20:41
ttxmost of them are in already20:41
ttxnot approving for any lib20:42
dhellmannok20:42
dhellmannttx: let me know if you want help approving those, but this may be another case where it's better to just have one person doing the step20:44
ttxOK, so that means, RC2 is not blocked at all on step 920:44
dhellmanndid we decide not to let the glanceclient minimum change through?20:45
dhellmannit seems like we would want that before rc2 if we're going to do it20:45
ttxas sdague said, it's only broken with ssl20:45
dhellmannok20:46
ttxI'd say it could use a bump, but not more necessary in release than say, the keystonemiddleware one20:46
ttxwe can releasenote a few of those "recommended libraries"20:46
dhellmannyeah20:47
ttxif they hapen not to be formally described in requirements.txt20:47
dhellmannand raise the minimum for master20:47
ttxyap20:47
dhellmannok, so I'm going to -2 the requested change for glanceclient in https://review.openstack.org/#/c/174773/20:47
ttxsounds good20:47
ttxhmm wait20:48
nikhil_kttx: just released py-glanceclient 0.17.1 (sub: [openstack-dev] [Glance] [all] python-glanceclient release 0.17.1 )20:48
ttxerr wat20:48
nikhil_k(we needed that for RC2 spin on some projects)20:48
nikhil_k(will get back when you are more free)20:49
ttxyeah, but we kind of said "no more library release until we say so"20:49
dhellmannyeah, nikhil_k , we have a lot of things going on right now and minimizing the changes that might cause failures is really important20:49
nikhil_kttx: on Tuesday, yesterday you asked me for a release remember?20:50
ttxnikhil_k: I said we would do one.20:50
nikhil_kdhellmann: this one fixes nova et.al booting of VMs20:50
nikhil_kw/ SSL20:50
ttxnikhil_k: we know what it fixes, we just didn't want any new lib release to break the world we spend days and night to unbreak20:51
ttxnow it may *not break* the world20:51
ttxbut last thig we need at this stage is new breakage due to rush20:51
nikhil_kok, what can we do now?20:52
ttxwell, damage is done, so let's see how it goes, I guess20:52
dhellmannhope for the best, and block it with a requirements change if it causes issues20:52
nikhil_kI checked the commits and it's tightly coupled to those related to ssk20:52
nikhil_kssl*20:52
nikhil_kttx: just to be a little more clear if it was not, this is on stable/kilo series (0.17.x)20:53
nikhil_kthe latest glanceclient is 0.18.020:53
nikhil_kI hope that kind of makes you both a little better?20:54
nikhil_kmakes you both feel*20:54
nikhil_k(long day already, sorry)20:54
dhellmannnikhil_k: we've been fighting blockages in several branches, so it doesn't really matter20:54
nikhil_kgah20:55
nikhil_kdhellmann: sorry about this. I can help if you need more people looking into issues20:55
dhellmannnikhil_k: let's see how things go20:56
ttxit /should/ be alright. We just didn't want to insert any more entropy at this point20:57
*** david-lyle_ has joined #openstack-relmgr-office20:58
dhellmannttx: I have dinner plans tonight, so I'm going to need to leave fairly soon to get ready20:59
ttxdhellmann: ack20:59
dhellmannwe're waiting for sean's patches in d-g and grenade, and bknudson's patches in keystone20:59
ttxgoing to bed now20:59
ttxFeels like we removed uncapping from the critical path anyway20:59
dhellmannother than that, I think we have the plan worked out and I can start approving things or asking the infra team to approve them20:59
ttxand I can tag RC2s20:59
* nikhil_k feeling confident :)20:59
*** david-lyle has quit IRC20:59
dhellmannoh, true, so I'll just treat those as normal baby-sitting changes tomorrow20:59
dhellmannttx: the keystone sync is a blocker for their rc221:00
dhellmannand the one for cinder, as well21:00
dhellmannttx: have a good night; I'll talk to you tomorrow morning21:02
ttxack21:04
*** david-lyle_ has quit IRC21:15
*** david-lyle has joined #openstack-relmgr-office21:15
*** david-lyle has quit IRC21:21
*** david-lyle has joined #openstack-relmgr-office21:37
*** david-lyle_ has joined #openstack-relmgr-office22:20
*** david-lyle has quit IRC22:20
*** david-lyle_ has quit IRC22:57
*** david-lyle has joined #openstack-relmgr-office23:24
thingeettx: thanks, verifying https://bugs.launchpad.net/cinder/+bug/144658323:58
openstackLaunchpad bug 1446583 in Keystone kilo "services no longer reliably stop in stable/kilo" [Critical,In progress] - Assigned to Brant Knudson (blk-u)23:58
thingeethe patch that is23:58

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