Monday, 2015-04-27

*** dims_ has quit IRC00:34
*** ttx has quit IRC01:18
*** ttx has joined #openstack-relmgr-office01:22
*** ttx has quit IRC06:47
*** ttx has joined #openstack-relmgr-office06:47
ttxmestery_: we don't *have to* (we issue security fixes post-release all the time) -- but that's certainly a good reason to do one.06:51
*** openstackstatus has joined #openstack-relmgr-office08:07
*** ChanServ sets mode: +v openstackstatus08:07
-openstackstatus- NOTICE: Restarting gerrit because it stopped sending events (ETA 15 mins)08:10
*** dims has joined #openstack-relmgr-office10:14
ttxjohnthetubaguy: saw https://bugs.launchpad.net/nova/+bug/1447380 ?10:20
openstackLaunchpad bug 1447380 in OpenStack Compute (nova) "wrong cinder.conf.sample generation: missing directives for keystone_authtoken (at least)" [Critical,In progress] - Assigned to John Griffith (john-griffith)10:20
ttxand https://bugs.launchpad.net/nova/+bug/144807510:22
openstackLaunchpad bug 1448075 in OpenStack Compute (nova) "Recent compute RPC API version bump missed out on security group parts of the api" [Critical,In progress] - Assigned to Hans Lindgren (hanlind)10:22
johnthetubaguyttx: eek, just looking through that to see if I understand what its doing10:30
sdagueso, honestly, that config generator code has been variously broken for a long time.10:57
*** sileht has quit IRC11:59
*** sileht has joined #openstack-relmgr-office12:09
ttxjohnthetubaguy, sdague: agreed, not sure I would respin on that one alone, but if there is a straightforward fix, I could consider merging it in case we do one (for example, to fix 1448075)12:33
johnthetubaguyttx: yeah, it was the security group one that worries me more12:34
sdaguejohnthetubaguy: which sec group bug?12:35
johnthetubaguysdague: the one mentioned above: https://bugs.launchpad.net/nova/+bug/144807512:35
openstackLaunchpad bug 1448075 in OpenStack Compute (nova) "Recent compute RPC API version bump missed out on security group parts of the api" [Critical,In progress] - Assigned to Hans Lindgren (hanlind)12:35
sdagueah, oops12:35
sdaguewe need to figure out a way to catch those RPC issues in code, they happen a bit too often12:36
johnthetubaguysdague: yeah, I think this one is more that we didn't complete the bump, I think the unit tests were not quite testing the correct thing in this case12:37
johnthetubaguyI thought it should have been caught by gate, but I its slight different sort of failure than on my first read through12:38
ttxjohnthetubaguy: so I think we'll do RC3 tomorrow morening over this one, if it's fixed in master and proposed for backport by then12:46
johnthetubaguyttx: OK, makes sense12:46
ttxI could consider adding the conf.sample thing if we somehow fix it to satisfaction. Happy to leave it out otherwise12:46
johnthetubaguyttx: +112:46
ttxjohnthetubaguy: so please give some attention to thos master reviews today if possible12:47
johnthetubaguyttx: +112:50
ttxdhellmann: I'd like to sort out the oslo.messaging stuff today12:52
ttxso ping me when around12:52
*** sileht has quit IRC12:52
*** dims has quit IRC13:17
*** dims has joined #openstack-relmgr-office13:18
*** russellb has quit IRC13:24
*** russellb has joined #openstack-relmgr-office13:28
*** superdan is now known as dansmith13:31
ttxmestery_: ping me when around13:32
*** sileht has joined #openstack-relmgr-office13:32
mestery_ttx: here13:32
*** mestery_ is now known as mestery13:32
ttxmestery: so there is bug 144788313:33
openstackbug 1447883 in OpenStack Security Advisory "Restrict netmask of CIDR to avoid DHCP resync is not enough" [Undecided,New] https://launchpad.net/bugs/144788313:33
mesteryttx: Yes, this is hte one we've been discussing asynchronously.13:33
mesteryttx: Ideally, we could get an RC3 for this (and perhaps one other one which merged Friday).13:34
mesteryttx: Thoughts?13:34
ttxI'll discuss it with the Vulnerability Managemt Team in 20min13:34
ttxbut yeah, since the issue is public that sounds like a nice thing to roll in release13:34
ttxHow safe is the patch there ?13:34
ttxmestery: and what is that other patch you're considering ?13:35
mesteryttx: I'm confident in the patch, we've all discussed it and we're good with adding it to a Kilo release candidate13:35
mesteryttx: Grabbing the other one13:35
ttxhttps://review.openstack.org/#/c/177738/ ?13:35
mesteryttx: https://review.openstack.org/#/c/177466/13:36
mesteryBut the one you referece is also woth adding13:36
mestery*worth13:36
ttxyeah13:37
mesteryttx: I had other report form someone tesitng RC1 that I'm examining now as well.13:37
mesteryHaven't digested it yet, give me about 20 minutes or so.13:37
ttxok, let's discuss it again in 30min13:37
mesteryttx: Works for me, thanks!13:37
*** morganfainberg has quit IRC13:44
*** morganfainberg has joined #openstack-relmgr-office13:47
-openstackstatus- NOTICE: gerrit has been restarted to clear a problem with its event stream. change events between 13:09 and 13:36 utc should be rechecked or have approval votes reapplied as needed to trigger jobs13:47
johnthetubaguydansmith: thanks, just wanted to be sure I wasn't missing something, yeah, I think it looks good minus the extra bit of testing14:02
dansmithjohnthetubaguy: yeah, I have no idea why it was done that way.. it's extremely error-prone14:03
dansmithjohnthetubaguy: originally, I mean. this patch is an improvement on multiple levels14:04
johnthetubaguydansmith: +1 I went digging in the git history, but lost the trail a little, I think we maybe got confused about where neutron would plugin in14:12
dansmithjohnthetubaguy: yeah, maybe14:12
ttxmestery: around ?14:25
mesteryttx: o/14:25
mesteryttx: This is the one I was talking about: https://bugs.launchpad.net/neutron/+bug/144881314:26
openstackLaunchpad bug 1448813 in neutron "radvd running as neutron user in Kilo, attached network dead" [High,In progress] - Assigned to Henry Gessau (gessau)14:26
ttxmestery: ok, so we can do a RC3 to catch that public security issue pre-release14:26
mesteryttx: Fix proposed to master, working on backport.14:26
mesteryttx: Cool14:26
ttxnow the question is more, what should we include in it14:26
mesteryYes14:26
ttxAt this point I'd like to leave anything that can be fixed post-release off14:26
mesteryttx: OK14:26
ttxunless already-fixed and obviously-safe14:27
mesteryRight14:27
ttxwhich may not be the case of 144881314:27
ttxbut let's see. I'll open the RC3 milestone first14:27
mesteryExcellent14:27
ttxhttps://launchpad.net/neutron/+milestone/kilo-rc3 opened with 1447883 in14:29
mesterycool14:29
ttxSo what else ?14:29
* mestery looks and courses his slow internet connection today14:29
mesterycurses even14:29
mesteryhttps://review.openstack.org/#/c/177466/14:29
mesteryThat one barely missed RC2, and would be nice to get in14:30
ttxI think https://review.openstack.org/#/c/177738/ makes sense pre-release14:30
mesteryAck, +2 on 17773814:31
ttxhttps://review.openstack.org/#/c/177466/ ... not sure. This seems more risky14:31
ttxcould be safely added to stabel/kilo after more baking in master14:31
ttxAdding https://bugs.launchpad.net/neutron/+bug/1441107 (to cover 177738)14:32
openstackLaunchpad bug 1441107 in neutron "Missing entry point for haproxy namespace driver" [High,Fix committed] - Assigned to Jakub Libosvar (libosvar)14:32
mesteryIt's hard to argue against that, though carl_baldwin will be a sadpanda :)14:32
ttxthe more we add the more we risk :)14:32
mesteryAgreed14:33
ttxYou should un-2 https://review.openstack.org/#/c/177187/14:33
mesteryDone14:33
ttxmestery: anything else that can't really be fixed post-release and/or is 100% safe ?14:34
mesteryI'd like to get https://bugs.launchpad.net/neutron/+bug/1448813 in, but it hasn't merged in master and we can likely release note and get it into the first dot release of kilo14:34
openstackLaunchpad bug 1448813 in neutron "radvd running as neutron user in Kilo, attached network dead" [High,In progress] - Assigned to Henry Gessau (gessau)14:34
mesteryAgree with taht assessment?14:35
ttxlet me look14:35
ttxThat one is arguably harder to fix post-release14:35
mesteryYeah, agreed.14:36
mesteryI need to find another core reveiwer to get it into master14:36
ttxalso arguably safe14:36
mesterykYesThen we14:36
mesteryYes14:36
ttxwould be the other way around I would -2 it14:36
mesteryWait, didn14:37
mesterydidn't follow that14:37
ttxwell, if the patch was about going from root to neutron-user rights, that would be more risky14:37
johnthetubaguyttx: https://review.openstack.org/#/c/177791/ is the backported for nova RC3, although its not quite merged in master yet14:37
mesteryah, got it14:37
ttxyeah, would be good to get a second +2 on that radvd thing, I'd like to cinlude it14:38
ttxI'll add it to RC314:38
mesteryFinding someone now.14:38
ttxmestery: let's try to wrap it up later today once that patch merges14:40
mesteryttx: Yes, working to get it landed. Thank you!14:40
ttxjohnthetubaguy: anything else being RC3 material ?14:40
johnthetubaguyttx: there are some policy fixes that could be nice to haves, but can be backported, and probably not worth the regression risk at this point14:42
ttxjohnthetubaguy: I'm fine doing a one-patch RC314:42
ttxjohnthetubaguy: we could wrap it up today14:42
ttxif you get the master fix in asap14:43
ttxjohnthetubaguy: let me open the milestone right now14:43
johnthetubaguyttx: OK, thank, thats a good plan I think14:43
johnthetubaguyttx: the change is approved, so it should be going through the system now14:43
ttxjohnthetubaguy: do you want to try to fix the config.sample file thing ?14:44
johnthetubaguyttx: actually, its worth a punt, given how much it will confuse users14:45
ttxI'm fine with leaving it out, but don't come back tomorrow with it :)14:45
ttxdavid-ly_: around?14:47
ttxredrobot: ping14:47
johnthetubaguyttx: well, maybe lets wait till tomorrow? this one just got mentioned to: https://bugs.launchpad.net/nova/+bug/144713214:49
openstackLaunchpad bug 1447132 in OpenStack Compute (nova) kilo "nova-manage db migrate_flavor_data doesn't do instances not in instance_extra" [Undecided,New]14:49
ttxjohnthetubaguy: ok, we could close it tomorrow morning during the 1:114:50
johnthetubaguyttx: thnaks14:51
ttxmorganfainberg: ping15:20
morganfainbergttx: pong15:20
ttxmorganfainberg: I'd like to ask you about doing kyestone libs kilo point releases15:21
morganfainbergttx: i was waiting for you to give me the all clear.15:21
ttxWe should have .Z for middelware and client to include latest security fix15:21
morganfainbergyes.15:21
ttxYou got it15:21
ttx(Announced on -dev earlier)15:21
morganfainbergttx: right.15:21
morganfainbergi'll get those ready to go today/tonight15:21
ttxIdeally we would wrap that up today, so that it doesn't collide with release timing15:21
* morganfainberg is at a conference15:22
morganfainbergbut i'll get it rolled up here / start doing it once I'm done with this session15:22
morganfainbergttx: so should we open new development series for the stables of ksc/middleware?15:23
morganfainbergttx: rather than just adding milestones?15:23
ttxmorganfainberg: it's still in the kilo series15:23
morganfainbergttx: these are semver15:23
morganfainbergttx: middleware wont switch to releasing on the 6mo cycle until Liberty15:24
ttxsure, that's fine15:24
morganfainbergttx: so i was just wondering if we wanted in LP a 1.<whatever> series15:24
morganfainbergvs. just wedging in 1.Y.Z milestones15:24
ttxno, I think I fixed up series in LP already15:25
morganfainbergok sounds good15:25
ttxlet me check15:25
morganfainbergaha i see kilo15:25
morganfainbergyou did15:25
morganfainberg:)15:25
* morganfainberg hadn't looked at the series for that.15:25
ttxyep created a kilo one, just push 1.5.1 there15:25
morganfainbergthanks.15:25
morganfainbergi'll get that moving today15:25
ttxand 1.3.1 on the other siude15:25
morganfainbergyep15:25
ttxcool thx15:25
ttxmorganfainberg: I take it keystone RC2 is not on fire yet ?15:26
ttxredrobot: you around?15:27
ttxdavid-lyle: or you ?15:28
morganfainbergttx: no issues with rc2 really. I don't think either proposed patches to stable warrant an rc315:31
ttxmorganfainberg: agreed, and getting less liekly by the hour15:31
redrobotttx o/15:37
ttxredrobot: Everything in RC2 merged, but a bug was added late:15:39
ttxhttps://bugs.launchpad.net/barbican/+bug/144786815:39
openstackLaunchpad bug 1447868 in Barbican kilo "Post of valid ACL returns 400" [Undecided,New]15:39
ttxTwo options here:15:39
ttx- Get it fixed real quick in master so that it can be part of Barbican release (without it needing to be deferred)15:39
ttx- Remove it from RC2 and get it fixed post-release in the stable branch15:39
ttxredrobot: At this point getting a RC2 for testing out is probably a good idea, so unless this bug totally prevents using Barbican (or you can get the fix in in the coming hours) I think we should remove it from the list and fix it post-release.15:40
redrobotttx I just proposed a CR with the fix a couple of minutes ago15:40
ttxredrobot: feeling confident it can get in soon ?15:40
redrobotttx yes, it's reviewed and about to merge in master15:41
ttxredrobot: can't find the ref15:41
ttxprobably missing bug ref in commit message15:41
ttxweird15:41
redrobotttx should be merged as soon as gerrit gets to it15:41
redrobotttx https://review.openstack.org/#/c/177827/ is the kilo CR15:41
ttxok, let's keep it in then15:42
ttxMay I cut RC2 once that is in ?15:42
redrobotttx yes,  please do so.15:42
ttxredrobot: alright, will keep you posted15:42
ttxredrobot: thx!15:43
morganfainbergTtx: is the middleware requirements update not a concern. I think that is still failing.15:50
ttxmorganfainberg: what  middleware requirements update ?15:50
morganfainberghttps://review.openstack.org/#/c/173972/15:54
ttxmorganfainberg: We've been pushing kilo libs out without those caps in, so that should be safe16:00
ttxdhellmann: ^16:00
morganfainbergOk. Just checking before I push tags.16:01
ttxmorganfainberg: basically not worse than what is in16:01
*** david-ly_ is now known as david-lyle16:01
ttxdavid-lyle: o/16:01
david-lylettx: o/16:01
ttxdavid-lyle: that bug was raised as critical: https://bugs.launchpad.net/horizon/+bug/144728816:02
openstackLaunchpad bug 1447288 in OpenStack Dashboard (Horizon) "create volume from snapshot using horizon error" [Critical,In progress] - Assigned to Masco Kaliyamoorthy (masco)16:02
ttxdavid-lyle: I /think/ it could be fixed post-release, but we could do a fast respin if a fix was posted really really fast16:02
david-lylewas just looking at tht16:02
ttxno idea how much of a showstopper it actually is16:03
david-lyleproposed fix looks really simple16:03
david-lylewould have to validate of course16:04
ttxyeah, looks relatively safe, so it's more a question of how unusable release is without it16:04
ttxMaybe we cna make a decision on that one duroing the 1:1 tomorrow ? If you want it, merge it in master and post a backport which we'll assess then ?16:05
david-lylesounds good. have to see if the proposed fix is enough16:06
david-lylewill know more by 1:116:07
ttxdavid-lyle: that works16:07
morganfainbergttx: 1.3.1 python-keystoneclient released, 1.5.1 keystonemiddleware16:40
morganfainbergttx: emails sent16:40
notmynamettx: I probably missed the note, but I need to update https://wiki.openstack.org/wiki/ReleaseNotes/Kilo right?16:55
dhellmannttx: I -2 all of the requirements updates17:02
ttxnotmyname: you do indeed18:21
notmynamettx: working on it now18:21
ttxnotmyname: was planning to remind everyone tomorrow on the 1:1sq18:21
*** johnthetubaguy is now known as zz_johnthetubagu20:06
nikhil_k_ttx: hi, around by chance?20:34
*** SlickNik has left #openstack-relmgr-office21:28
ttxnikhil_k_: yes, but about to go21:37
nikhil_k_ttx: just one quick question21:38
nikhil_k_ttx: how long before we absolutely need to have the sessions in the sched official list?21:39
nikhil_k_ttx: would Thusday before the summit work?21:39
nikhil_k_May 14th?21:39
nikhil_k_trying o plan some meetings21:39
ttxThat would be rather late21:39
ttxI'd rather have the schedule mostly nailed around the 8th, so that people can plan attendance21:40
ttxbut then, they know it's a Glance session21:40
nikhil_k_Thanks. Noted.22:50
*** dims has quit IRC23:46

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