Tuesday, 2015-04-21

*** openstack has joined #openstack-relmgr-office00:36
*** flaper87 has quit IRC05:01
*** flaper87 has joined #openstack-relmgr-office05:04
*** mestery has quit IRC07:03
*** flaper87 has quit IRC07:23
*** flaper87 has joined #openstack-relmgr-office07:23
*** mestery has joined #openstack-relmgr-office07:46
ttxasalkeld: grabbing coffee, be there in a minute07:59
asalkeldok08:01
ttx#startmeeting ptl_sync08:02
openstackMeeting started Tue Apr 21 08:02:36 2015 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.08:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.08:02
ttx#topic Heat08:02
openstackThe meeting name has been set to 'ptl_sync'08:02
ttxasalkeld: hi!08:02
asalkeldhi08:02
ttxso... RC208:03
asalkeldso we have a heap of https://bugs.launchpad.net/heat/+bugs?field.tag=kilo-rc-potential08:03
asalkeldin fix commited08:03
ttxand a few proposed for backport already08:03
asalkeldyeah08:04
ttxLet's open a RC2 and see which bugs should be added to it08:04
asalkeldok08:04
ttxAt this stage we'll only accept bugs that are already fixed in master08:04
asalkeldmakes sense08:04
asalkeldwhat is the timeline?08:04
ttxhttps://launchpad.net/heat/+milestone/kilo-rc208:04
ttxThe idea would be to close it Thursday at the latest08:05
ttxdepending on how the library requirements mess untangles08:05
asalkeldok, so we need to proprose these quickly08:05
ttxSo let's see your list08:05
ttxhttps://bugs.launchpad.net/heat/+bugs?field.tag=kilo-rc-potential&orderby=-status&start=008:05
asalkeldthere are 1108:06
ttx(I see 9)08:06
asalkeldyeah, 2 in incomplete08:06
ttxhttps://bugs.launchpad.net/heat/+bug/143715808:06
openstackLaunchpad bug 1437158 in heat "Module novaclient.v1_1 is deprecated" [Medium,Fix committed] - Assigned to Michal Rostecki (mrostecki)08:06
ttxwondering if that's the best moment to change that08:07
asalkeldso the patch tries v2 else falls back to v108:08
asalkeldthe client copied v1 to v208:08
asalkeld(from what i saw)08:08
*** zz_johnthetubagu is now known as johnthetubaguy08:08
ttxhmm08:08
ttxasalkeld: if you think it's totally safe, I guess we can get it in. It's just not really a bug, more of a leftover feature08:09
asalkeldhttps://github.com/openstack/python-novaclient/commit/0a60aae852d2688861d0b4ba097a1a00529f061108:09
ttxand RC2 is a very late stage to add that08:09
asalkeldRename v1_1 to v208:09
asalkeldand add deprecation messages all over the place08:09
ttxok08:09
ttxsounds like a useful prerelease cleanup08:10
asalkeldi think it's ok08:10
ttxadding08:10
ttxhttps://bugs.launchpad.net/heat/+bug/143897808:10
openstackLaunchpad bug 1438978 in heat "The internal create_stack interface misses 'parent' parameter" [High,Fix committed] - Assigned to Angus Salkeld (asalkeld)08:10
asalkeldyip, that's important08:10
asalkeldso ttx do i set the milestone to rc2 ?08:11
asalkeldas it's in master already08:11
ttxI'm doing it (you have to create the kilo task so it's a bit weird08:11
ttxThat one sounds like a large patch too08:12
ttxsafe?08:12
asalkeldyeah, better in than out08:12
ttxok08:12
asalkeldregression from a blueprint we did08:12
ttxhttps://bugs.launchpad.net/heat/+bug/143949708:13
openstackLaunchpad bug 1439497 in heat "No Ip assigned to server after update" [High,Fix committed] - Assigned to huangtianhua (huangtianhua)08:13
ttxlooks safe08:13
asalkeldyip08:14
ttxhttps://bugs.launchpad.net/heat/+bug/143970808:14
asalkeldwow git.openstack.org is slow08:14
openstackLaunchpad bug 1439708 in heat "stack update fail when server has a port" [High,Fix committed] - Assigned to Ethan Lynn (ethanlynn)08:14
ttxAlso better fixed pre-release08:15
*** johnthetubaguy is now known as zz_johnthetubagu08:15
asalkeldyeah that's good08:15
ttxhttps://bugs.launchpad.net/heat/+bug/143995908:15
openstackLaunchpad bug 1439959 in heat "heat db field nullable is True by default" [Wishlist,Fix committed] - Assigned to Kanagaraj Manickam (kanagaraj-manickam)08:15
asalkeldthat's a cleanup08:16
ttxThat one sounds like it could bear some risk08:16
asalkeldshouldn't actually effect anything08:16
ttxoh, that's the default ?08:16
ttxok then08:16
ttxhttps://bugs.launchpad.net/heat/+bug/144325208:17
openstackLaunchpad bug 1443252 in heat "sql migration failed on db2" [Medium,Fix committed] - Assigned to Ethan Lynn (ethanlynn)08:17
asalkeldthat's is fine, only effects db208:17
ttxthat one is safe since it's DB2-cased08:17
ttxhttps://bugs.launchpad.net/heat/+bug/144408708:17
openstackLaunchpad bug 1444087 in heat "SoftwareDeployments don't work for non-CREATE actions" [High,Fix committed] - Assigned to Steven Hardy (shardy)08:17
ttxsounds useful08:18
asalkeldyeah08:18
asalkeldonly effects on resource08:18
ttxhttps://bugs.launchpad.net/heat/+bug/144517008:18
openstackLaunchpad bug 1445170 in heat "get_file doesn't notice changes during update" [High,Fix committed] - Assigned to Zane Bitter (zaneb)08:18
ttxlooks good to go too08:19
asalkeldyeah, fine08:19
ttxhttps://bugs.launchpad.net/heat/+bug/141588708:19
openstackLaunchpad bug 1415887 in heat "ValueError: AES key must be either 16, 24, or 32 bytes long" [Medium,Fix committed] - Assigned to rajiv (rajiv-kumar)08:19
*** zz_johnthetubagu is now known as johnthetubaguy08:20
ttxarh, string update there08:20
asalkeldthat's just a startup error on wrong config08:20
ttxI'd rather leave that one out08:21
asalkelddo you want to hold it?08:21
asalkeldok08:21
asalkeldnot a big deal08:21
ttxYou said you had two incomplete ones that you would like to investigate and potentially include ?08:22
asalkeldttx: they don't look bad08:22
asalkeldwe can backport later if needed08:22
ttxOK, let's revisit them just before we cut the RC2, in case they are fixed then08:22
ttxOtherwise let's go with the list @ https://launchpad.net/heat/+milestone/kilo-rc208:23
asalkeldok, looks good08:23
ttxTwo of them are already proposed (I set them to InProgress)08:24
asalkeldi'll work on backporting08:24
ttxThat leaves 6 to backport08:24
asalkeldok08:24
ttxI'll validate them once they are in08:24
asalkeldthanks!08:24
ttxThanks!08:24
ttxjohnthetubaguy: o/08:25
johnthetubaguyttx: hi08:25
ttx#topic Nova08:25
ttxOK, so let's open RC2 and see what we can put in08:26
johnthetubaguycool08:26
*** asalkeld has left #openstack-relmgr-office08:26
johnthetubaguydo we just target to the milestone at this point?08:26
ttxhmm, we also need to cvreate the kilo task I think08:27
ttxhttps://bugs.launchpad.net/nova/+bugs?field.searchtext=&orderby=-importance&field.status%3Alist=FIXCOMMITTED&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_commenter=&field.subscriber=&field.structural_subscriber=&field.tag=kilo-rc-potential&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=&field.has_branches=on&fiel08:27
ttxd.has_no_branches.used=&field.has_no_branches=on&field.has_blueprints.used=&field.has_blueprints=on&field.has_no_blueprints.used=&field.has_no_blueprints=on&search=Search08:27
ttxerr08:27
ttxhttps://bugs.launchpad.net/nova/+bugs?orderby=-importance&field.status%3Alist=FIXCOMMITTED&field.tag=kilo-rc-potential08:28
ttxLet's go down that one ^08:28
johnthetubaguyyep08:28
ttxI suspec tthe 3 critical ones are really critical ?08:28
johnthetubaguyyeah, I mean they could be high, but they are all bad08:29
johnthetubaguythe API one is critical08:29
ttxok, targeting them all08:29
ttxhttps://bugs.launchpad.net/nova/+bug/98499608:30
openstackLaunchpad bug 984996 in OpenStack Compute (nova) "Instance directory does not exist: Unable to pre-create chardev file console.log" [High,Fix committed] - Assigned to Matt Riedemann (mriedem)08:30
ttxan oldie08:30
ttxit's rare that those get fix in a RC08:30
ttxsimple patch, +1 for me08:30
johnthetubaguyyeah, +108:31
johnthetubaguyhttps://review.openstack.org/#/c/173099/08:31
ttxhttps://bugs.launchpad.net/nova/+bug/143360908:31
openstackLaunchpad bug 1433609 in OpenStack Compute (nova) "Not adding a image block device mapping causes some valid boot requests to fail" [High,Fix committed] - Assigned to jichenjc (jichenjc)08:31
ttxsounds like a regression08:32
johnthetubaguy+108:32
ttxsays "then we can revert the nova client exception"... does that mean there is a companion patch ?08:33
ttxbah novaclient08:33
johnthetubaguyyeah, we can ignore that bit I think08:33
johnthetubaguylooks like it adds something back into novaclient08:33
ttxhttps://bugs.launchpad.net/nova/+bug/144096808:34
openstackLaunchpad bug 1440968 in OpenStack Compute (nova) "AttributeError: 'module' object has no attribute 'DatastorePath'" [High,Fix committed] - Assigned to Sabari Murugesan (smurugesan)08:34
ttxpretty straightforward08:34
johnthetubaguy+108:34
ttxhttps://bugs.launchpad.net/nova/+bug/144260208:35
openstackLaunchpad bug 1442602 in OpenStack Compute (nova) "live migration fails during destination host check" [High,Fix committed] - Assigned to Dan Smith (danms)08:35
johnthetubaguy+1 for that one too really08:35
johnthetubaguysmall fix08:35
ttxlegit08:35
ttxhttps://bugs.launchpad.net/nova/+bug/144402108:36
openstackLaunchpad bug 1444021 in OpenStack Compute (nova) "HostState.consume_from_instance fails when instance has numa topology" [High,Fix committed] - Assigned to Przemyslaw Czesnowicz (pczesno)08:36
ttxFeels a bit more specialized, but probably isolated enough08:37
johnthetubaguyyeah, its a possible08:37
ttxlet's add it08:37
ttxhttps://bugs.launchpad.net/nova/+bug/144430008:38
openstackLaunchpad bug 1444300 in OpenStack Compute (nova) "nova-compute service doesn't restart if resize operation fails" [High,Fix committed] - Assigned to Rajesh Tailor (rajesh-tailor)08:38
johnthetubaguy+1 for that, its a simple fix really08:38
ttxack08:38
ttxhttps://bugs.launchpad.net/nova/+bug/144472808:39
openstackLaunchpad bug 1444728 in OpenStack Compute (nova) "KeyError: 'uuid' trace in n-cpu logs when logging with instance=instance kwarg" [High,Fix committed] - Assigned to Matt Riedemann (mriedem)08:39
ttx+1 fropm me08:39
johnthetubaguy+108:40
ttxhttps://bugs.launchpad.net/nova/+bug/144504008:40
openstackLaunchpad bug 1445040 in OpenStack Compute (nova) "InstancePCIRequests.obj_from_db fails to get requests from db" [High,Fix committed] - Assigned to Przemyslaw Czesnowicz (pczesno)08:40
ttxsounds simple enough08:41
ttxadded08:41
ttxhttps://bugs.launchpad.net/nova/+bug/143823808:41
openstackLaunchpad bug 1438238 in OpenStack Compute (nova) "Several concurent scheduling requests for CPU pinning may fail due to racy host_state handling" [Medium,Fix committed] - Assigned to Nikola Đipanov (ndipanov)08:42
ttxsince we accepted the other part...08:42
johnthetubaguyyeah08:42
johnthetubaguyit seems sound08:43
ttxok08:43
ttxhttps://bugs.launchpad.net/nova/+bug/144116908:43
openstackLaunchpad bug 1441169 in OpenStack Compute (nova) "can't schedule vm with numa topology and pci device" [Medium,Fix committed] - Assigned to Przemyslaw Czesnowicz (pczesno)08:43
ttxhrm08:44
johnthetubaguyyeah, bumps a version number for an object08:44
ttxright08:44
ttx"one of the BPs completed in Kilo is completely broken without the patch"08:44
ttxnot sure about the impact of bumping a microversion so late08:45
johnthetubaguyits a now or never, so I guess we should add it?08:45
ttxyeah08:45
ttxI feel like it's disruptive, but otherwise won't be in kilo at all08:45
johnthetubaguyyeah08:45
ttx+108:45
ttxLet's cut it soon enough to detect breakage though08:45
ttxhttps://bugs.launchpad.net/nova/+bug/134006808:46
openstackLaunchpad bug 1340068 in OpenStack Compute (nova) "Useless option mute_weight_value" [Low,Fix committed] - Assigned to Davanum Srinivas (DIMS) (dims-v)08:46
johnthetubaguyttx: thats a good point08:46
ttxhmm, string change here08:46
ttxalso a change in defaults08:47
johnthetubaguyyeah, I think this has missed the boat, only really got merged as liberty was open08:47
johnthetubaguyI need to go back an update the message, sadly08:47
ttxyeah08:48
ttxdeprecated in 2015.208:48
ttxI'd leave that one out at this point08:48
johnthetubaguy+1 for leaving that, mostly due to the string08:48
johnthetubaguyits not worth all the hoops we need for that08:48
ttxok removing tag08:48
ttxok, that gives: https://launchpad.net/nova/+milestone/kilo-rc208:49
ttxchecking the match with the currently-proposed backports08:49
ttxjohnthetubaguy: we have a backport for https://bugs.launchpad.net/nova/+bug/1444630 proposed too08:51
openstackLaunchpad bug 1444630 in OpenStack Compute (nova) "nova-compute should stop handling virt lifecycle events when it's shutting down" [Medium,Fix committed] - Assigned to Matt Riedemann (mriedem)08:51
ttxand for https://bugs.launchpad.net/nova/+bug/142909308:51
openstackLaunchpad bug 1429093 in OpenStack Compute (nova) "nova allows to boot images with virtual size > root_gb specified in flavor " [Medium,Fix committed] - Assigned to Roman Podoliaka (rpodolyaka)08:51
johnthetubaguyah, its marked as a backport potential08:52
ttxwhat is your call on it ?08:53
ttx(1444630)08:53
johnthetubaguyso I looked at this in the wrong order08:54
johnthetubaguy1429093 is almost a security thing08:54
ttxyeah, that one sounds like a worthy thing08:55
ttxadding08:55
ttxwhat about https://bugs.launchpad.net/nova/+bug/144463008:56
openstackLaunchpad bug 1444630 in OpenStack Compute (nova) "nova-compute should stop handling virt lifecycle events when it's shutting down" [Medium,Fix committed] - Assigned to Matt Riedemann (mriedem)08:56
ttxsounds also pretty safe08:56
johnthetubaguyyeah, I think thats a nice small fix08:56
ttxadded08:57
ttxlast one08:57
ttxhttps://review.openstack.org/#/c/174066/08:57
ttxno bug reference08:57
ttxhttps://bugs.launchpad.net/nova/+bug/144567508:58
openstackLaunchpad bug 1445675 in OpenStack Compute (nova) "missing index on virtual_interfaces can cause long queries that can cause timeouts in launching instances" [Undecided,In progress] - Assigned to Mike Bayer (zzzeek)08:58
ttxthat would be this one08:58
ttxnot in master yet08:58
ttxI'll -2 it as not being in master yet08:58
johnthetubaguyyep08:58
ttxOK, final list at https://launchpad.net/nova/+milestone/kilo-rc208:59
ttxWe'll need 4 extra backports08:59
ttxI'll approve soon08:59
ttxjohnthetubaguy: I think that is all -- ttyl09:00
johnthetubaguyttx: OK, thanks, do we want to look at the ones that are not yet committed that might block releasing RC2?09:00
johnthetubaguyactually, I am not sure there are any now09:00
ttxjohnthetubaguy: do you have any ?09:00
ttxLet's reconsider when we are close to cutting RC209:01
johnthetubaguythere was one, but I just downgraded it09:01
ttxi.e. tomorrow/Thursday09:01
johnthetubaguyttx: I was just going to ask, cool09:01
johnthetubaguyttx: need those backports first I guess09:01
johnthetubaguyttx: thanks, thats everything now I think09:01
ttxarh, looks like I shouldn't have created those kilo tasks and just reuse the release thing09:02
ttxwillfix09:02
ttxdamn Lp09:02
johnthetubaguyttx: ah, why is that?09:04
ttxlong story09:04
johnthetubaguyno worries09:04
johnthetubaguyso we are just doing targeting to milestones for this?09:05
ttxin previous releases we'd rely on FixCommitted = fixed in master / FixReleased = fixed in milestone09:05
johnthetubaguyah, that rings a bell09:05
ttxrather than use series tasks09:05
johnthetubaguyavoids the slow LP query bugs I guess09:05
ttxbut that was relying on the Gerrit/LP updater specialcasing proposed/*09:05
ttx(and turning bugs there to FixReleased on merge)09:06
ttxNow that we use stable/kilo things are borken09:06
ttxI need to fix that09:06
ttxtwo options: use kilo tasks (and have them closed at RC delivery time)09:06
ttxor...09:07
ttxsomehow make the Gerrit/LP updated understand what it needs to do09:07
ttxwithout the help of the branch name09:07
johnthetubaguyah, gotcha09:07
johnthetubaguynasty09:07
ttxmight actually be simpler to use kilo tasks09:07
johnthetubaguyit seems clear at least09:08
ttxhmm, will think a bit more about it09:08
ttxin the meantime lets us spot which backports are missing, which is a plus09:09
johnthetubaguy+109:15
johnthetubaguyttx: we have backports ready for those other bugs now: https://launchpad.net/nova/+milestone/kilo-rc210:03
ttxack, will approve soon10:09
ttxno hurry, we'll need requirements bumps in and those are not solved yet10:10
ttxjust approved the backlog so that we don't build a huge one10:10
sdaguettx: so... hmm... I think I just found another cross cutting critical openstack bug related to oslo :(10:52
sdaguestable/kilo services can not reliably shutdown10:52
sdaguethe oslo.service code seems to be losing children10:53
sdaguethis is incubator code, so if this is really the bug, we're going to need to respin everyone10:54
ttxsdague: well, better now than next week11:08
ttxbut we'll need a solution soon so that we can include it in the RC2s we are opening right now11:08
sdagueyeh, well we'll need oslo folks to go active around this, I just brought it up in channel11:09
sdaguethe exposure is we can't add stable/kilo -> liberty testing in our infrastructure, because the grenade jobs fail too often trying to shutdown processes - https://review.openstack.org/#/c/175391/11:10
sdagueso the d-g change keeps getting blocked11:10
sdaguehow do you want to track something like this?11:10
ttxhmm, ideally a bug with a task in every consuming servcie11:11
ttxpraying that LP will behave11:11
ttxFor the time being, you can create a bug that would at least include keystone, heat and nova, since that is the current RC2 windows we have11:12
ttxI suspect swift is not affected ?11:12
sdagueso, I've seen keystone and cinder choke on it11:13
ttxSergeyLukjanov: we can talk now so that we get more time to discuss RC211:24
sdaguettx: https://bugs.launchpad.net/oslo-incubator/+bug/144658311:27
openstackLaunchpad bug 1446583 in oslo-incubator "services no long reliably stop in stable/kilo" [Critical,New]11:27
ttxthx. As soon as it's confirmed and we have some clue into how to fix it, I'll create RC2 tasks for it11:28
sdaguedims was the approver on a lot of that code, so I'm hoping he'll have ideas11:33
sdaguebut, he's not around atm?11:33
sdagueok, I added keystone and cinder to the bug11:42
sdagueand put in everything I could about what I'm seeing11:42
SergeyLukjanovttx, hi, sorry, I've been on a lunch11:51
SergeyLukjanovttx, I'm ready if you are11:51
ttxok, let's do this11:51
ttx#topic Sahara11:51
SergeyLukjanovwe have no critical issues found for rc211:51
ttxI see nothing fixcommitted in kilo-rc-potezntial11:52
ttxSomeone proposed https://review.openstack.org/#/c/175026/11:52
SergeyLukjanovthe only potential thing - fix a few links in docs (will be useful for users, but it's mostly nice to have)11:52
ttxSergeyLukjanov: we'll certainly do a RC2 to catch up requirements / translations11:53
SergeyLukjanovttx, yup, I think we can do it after release - it's a bunch of testing scenario files11:53
ttxso we could include "nice to have" clearly safe stuff11:53
SergeyLukjanovokay, that's great, I'll make a patch soon11:54
ttxbut if nothing urgent and RC1 still lookg good for testing, we should keep it around for a few days11:54
ttxLet's plan to do a RC2 at the end of the week11:54
ttxto catch up the last stuff11:54
SergeyLukjanovokay11:55
ttxhttps://review.openstack.org/#/c/175026/11:55
ttxAbout this one ^11:55
ttxIf we do a RC2 anyway, would you include it ?11:55
SergeyLukjanovso, I think then we'll have in addition to requirements - https://review.openstack.org/#/c/175026/ , small change in docs11:55
ttxIf yes, could you have a bug for it and tag it kilo-rc-potential ?11:55
SergeyLukjanovyup, it'll enable useful11:55
SergeyLukjanovwill do11:55
ttxsame for the change in docs11:55
SergeyLukjanovsure11:55
ttxso that it's on the RC2 radar11:55
ttxOK, and let's plan to talk again, say, Thursday11:56
SergeyLukjanovttx, ack, thx11:56
ttxAbout the Design Summit layout for Sahara, did you have time to look into it ?11:56
SergeyLukjanovttx, I think that we'll be ready to tag rc2 at Thu11:56
ttxjust toi check it's not completely crazy11:56
ttxhttps://docs.google.com/spreadsheets/d/1VsFdRYGbX5eCde81XDV7TrPBfEC7cgtOFikruYmqbPY/edit?usp=sharing11:57
ttxA few work sessions on Wed, then most sessions Thursday afternoon11:58
SergeyLukjanovttx, yup, we discussed the number of slots (2-5-2) with team on irc meeting and we think that it's okay11:58
SergeyLukjanovttx, re layout it seems ok I think11:58
ttxok. It's too hard to change anyway :)11:58
SergeyLukjanovheat and infra at the same time looks a bit sad for me, but I understand11:59
ttxYeah, tried to reduce that conflict, at least fishbowls don't collide11:59
SergeyLukjanovttx, yeah12:00
SergeyLukjanovttx, so, IMO it looks very nice12:00
SergeyLukjanovttx, I like this fragmentation, I think it'll increase a chance for cross project communication12:01
ttxwell, we'll see12:01
ttxSergeyLukjanov: ttyl!12:01
*** eglynn has joined #openstack-relmgr-office12:01
ttxeglynn: o/12:01
eglynnhey12:01
ttx#topic Ceilometer12:01
SergeyLukjanovttx, thx12:01
eglynnstill nada in https://bugs.launchpad.net/ceilometer/+bugs?field.tag=kilo-rc-potential12:02
ttxeglynn: I see no bug in the kilo-rc-potential list12:02
eglynnso I think we're looking realtively good12:02
eglynnIIRC 5 fixes have landed on liberty so far12:02
ttxthere was a proposed backport though12:02
eglynnnone higher than medium12:02
ttxactually two12:02
ttxhttps://review.openstack.org/#/c/174049/12:02
ttxbug 144620112:02
openstackbug 1446201 in Ceilometer "gnocchi alarm: url endpoint for validating query is wrong" [Medium,In progress] https://launchpad.net/bugs/1446201 - Assigned to Mehdi Abaakouk (sileht)12:02
ttxand...12:03
ttxhttps://review.openstack.org/#/c/175807/12:03
ttxbug 144522712:03
openstackbug 1445227 in Ceilometer "hbase should not use message_signature as unique id" [Medium,Fix committed] https://launchpad.net/bugs/1445227 - Assigned to ZhiQiang Fan (aji-zqfan)12:03
eglynnboth medium bugs12:03
ttxeglynn: we'll certainly do a RC2 anyway to catch requirements/translations12:03
ttxAt this point we can still keep RC1 around a couple more days12:04
eglynngenerally rc2 would only be for critical issues, amiright?12:04
ttxwell, we trigger a respin only for critical issues12:04
ttxbut once the respin is decided, we can look for obviously-safe backports12:04
eglynna-ha, so you're saying that we could pull in those two medium bugs since we're doing an RC2 anyway for other reasons12:05
eglynngot it12:05
ttxsince we'll respin to include the synced requirements anyway, we can look into things that would make sense to backport in the same run, low-risk12:05
eglynnso in that case, both relatively sane ... I'll review in detail and get them landed12:05
ttxthat said, your RC1 looks good enough to be testable for a few more days12:05
ttxso no hurry there12:05
eglynncool12:05
ttxI propose we discuss again on Thursday and see what to include in the respin12:06
eglynnsounds good12:06
eglynn(I'm on PTO tmrw BTW)12:06
ttxeglynn: ack12:06
ttxThe other topic I wanted to discuss is python-ceilometerclient12:06
ttxI noted you may want to do a stable/kilo re-release12:07
ttxis that needed to fix a specific bug ?12:07
ttxIf not, maybe a liberty featureful release is the best way forward12:07
ttxoh, that was done already (1.1.0)12:08
ttxso the question is more, do we need a 1.0.1412:08
eglynngordc has been working on a bunch of backports, I need to check with him when he comes online which of those he wanted to include (i.e. are all landed yet)12:08
ttxI understand that means "yes" ?12:09
eglynnyes to 1.0.14, not sure on the exact timing12:09
ttxbut no need to bump the min version there12:09
ttxwe can't do any release just now anyway12:09
ttxwe need to fix stuff[tm] first12:09
eglynnsure12:09
eglynnmin version == z-version in SEMVER terminology?12:10
ttxeglynn: could you check if there would be an12:10
ttxarh12:10
ttxany reason to bump the min version in stable/kilo requirements (to >=1.0.14 <1.1.0)12:10
eglynna-ha, that min version, the lower version bound12:11
ttxyep12:11
ttxthe best answer would be "no"12:11
eglynnok, will do, I've a call with gordc in ~90 mins, can discuss then12:11
ttxsince otherwiuse that triggers requirements updatexws12:11
ttxupdates*12:11
eglynnyeap, got it12:11
ttxto other projects12:11
ttxI think that is all...12:12
eglynncool, thanks for your time12:12
ttxAsl gordc to look into the DS ceilometer track layout12:12
ttxAsk*12:12
eglynncool, will do ... where is that published?12:12
ttxhttps://docs.google.com/spreadsheets/d/1VsFdRYGbX5eCde81XDV7TrPBfEC7cgtOFikruYmqbPY/edit?usp=sharing12:13
eglynncool12:13
ttx(sent an email to list about it last wek)12:13
ttx+e12:13
ttxwould be good to know if you still want that extra fishbowl slot, because it conflicts with one of your workroom slot12:14
ttxso I'll need to shuffle schedule if you want it12:14
eglynnslightly fragmented track12:14
eglynnbut I guess non-contiguous is probably the norm now12:14
ttxThey are all fragmented, yes12:14
eglynni.e. with all the additional projects in the mix12:14
eglynnyeap12:14
ttxCeilo is actually not that fragmented12:14
eglynnyeap, I've seen worse in past summits :)12:15
ttxThe goal is also to avoid block overlaps12:15
ttxlike "all cinder sessions collide with all ceilometer sessions, no way to be together"12:15
eglynnyeap, makes sense12:15
ttxfor a fragmented track, look at keystone :)12:15
ttxok, will talk to you again on Thursday12:16
eglynnyeah, true that12:16
eglynn... and as always Nova just conflicts with everything else :)12:16
eglynncoolness, talk to you then12:16
ttxdhellmann: ready when you are12:17
dhellmannttx: o/12:17
ttxdhellmann: you are back!12:17
ttxLots of stuff to discuss.12:18
dhellmannyes! sorry for the ill-timed disappearance12:18
ttx#topic Oslo12:18
ttxNo problem, I think we made great progress over the weekend and on Monday12:18
ttxenough to open RC2 windows now12:18
ttxThe idea being stable/kilo is in pretty good shape right now12:18
dhellmanncool - I started scanning the-big-thaw but might need a walk-through of the current status12:19
ttxthe fuckup is more around mastre requirements and libraries12:19
ttxso..12:19
ttxlet me walk through it12:19
ttxWe got all the .gitreview pushed to libs, except ezaqarclient which is borken on all branches12:19
ttxWe got all the uncap-requirements in master merged12:20
dhellmannI saw flavio's note about zaqar, so maybe we're not worried about fixing that for now?12:20
ttxexcept swiftclient (which doesn't sync anyway) and zaqarclient (borken as mentioned above)12:20
ttxright, I propose we ignore zaqarclient, not imported anywhere anyway12:20
dhellmann++12:20
flaper87++12:20
flaper87I'm working on that, though.12:21
ttxSo we are at the "release libraries with updated requirements (no caps)"12:21
flaper87I need to figure out the right way to enable pooling in the gate12:21
ttxbasically we need to make liberty releases for all libs with uncapped reqs12:21
dhellmannflaper87: ok, we can address the problem when the status of the project is decided, but make it low priority for now12:21
ttxbefore we reenable the tests and syncs12:21
dhellmannttx: ok, I can work on that today, assuming I have the required powers12:21
ttxOn the stable/kilo side, I fixed all branches and got the .gitreview merged in all projects12:22
ttxso we opened RC2 windows for some projects alreadyt12:22
dhellmannnice! there were a few jobs to disable, did that happen, too?12:22
ttxWe still block on stable/kilo library point release12:22
ttxdhellmann: yes12:22
dhellmannwhat's blocking the library point releases? process or gate jobs?12:22
ttxso we can't really "close" the windows we opened until we can mertge the final requirements bumps12:22
ttxwe need the "release libraries with updated requirements" step to be completed first12:23
ttxotherwise we bvreak the world12:23
ttxbasically master MUST find the liberty uncapped lib12:23
ttxnot our stable/kilo point release woth capped reqs12:23
dhellmannah, got it12:23
ttxso yeah, relkeasing those liberty libs is pretty time-sensitive, and I'd welcome your help in solving that12:24
ttxYou can do oslo first12:24
dhellmannyeah, I can do that this morning right after breakfast12:24
* dhellmann needs at least one cup of tea before cutting releases12:24
dhellmannI can go ahead and do all of them, if you'd like12:24
ttxSo that is one thing. The other exciting topics are issues in oslo libs /incub12:24
ttxwe have oslo.messaging needing a stable/kilo point release for https://bugs.launchpad.net/oslo.messaging/+bug/143676912:25
openstackLaunchpad bug 1436769 in oslo.messaging "ConnectionError: Too many heartbeats missed" [Critical,Confirmed] - Assigned to Mehdi Abaakouk (sileht)12:25
ttxWe have sdague's recent oslo.service issue at https://bugs.launchpad.net/oslo-incubator/+bug/144658312:25
openstackLaunchpad bug 1446583 in oslo-incubator "services no long reliably stop in stable/kilo" [Critical,New]12:25
ttxthe latter needing urgent attention since we'll have to copypaste the code back to every project in RC212:26
ttx(if genuine)12:26
ttxLast topic would be.. when/where to cut stable/kilo for the incubator12:26
ttxwe decided last time to do it when every RC1 is cut12:27
ttxbut we may want to do that once we solve 144658312:27
dhellmannyes, that would be more convenient12:27
ttxdhellmann: I think that is all.12:27
ttx:)12:27
dhellmannso the oslo.messaging release will be taken care of once we have the requirements issues in master resolved and all of those libraries are released12:27
ttxMost of those items are somewhere in the etherpad, fwiw12:28
dhellmannI need to find someone to look at that bug, though12:28
dhellmannok, good, I'll re-read now that I have the context for highlights12:28
ttxyeah, oslo.messaging doesn't need work, it's just blocked on the master requirements unwind at this point12:28
ttxlike everything else12:28
dhellmannright12:28
ttxI'll be busy with RC2 tracking today, so I'd rather have you own the liberty lib release thing entirely12:29
dhellmannok, I'll do all of the releases12:29
ttxMy underatsngin is that we need to release everything (even those which already have liberty releases) to catch the uncapped reqss12:29
dhellmannttx: is the list of libs starting on line 148 of the etherpad complete?12:29
dhellmannyes, that's what I would expect12:29
ttxdhellmann: It correspon,ds to the uncap-requirements merges12:30
ttxI noticed it excludes glnce_store12:30
dhellmannfor each I need to verify that the requirements.txt in the lib is currently not showing caps and then cut a new minor release12:30
ttxbut then that one seems to not have caught the caps in the first place12:30
dhellmannok, I'll add that to the bottom12:30
ttxsame for ceilometermiddleware12:30
dhellmannnoted12:31
dhellmannif they don't have caps in their current release, I think we can skip releasing new copies12:31
ttxIdeally we would go through most of step 9 (from the etherpad) today, so that we can do stable/kilo lib releases starting tomorrow12:32
ttxand so that we could announce depfreeze end on master too12:33
dhellmannagreed12:33
dhellmannI do have some other spec work I had hoped to do today, but I can put that off until tomorrow12:33
ttxI'll be around if you need sanity checking for anything12:33
dhellmannok. I'll start by making a complete list of the planned releases and their version #s12:34
ttxyep, and find someone to look into that oslo.service thing12:35
dhellmannttx: I probably don't have rights to create milestones in LP for a lot of these projects, so I'll just skip that step12:35
dhellmannyep12:35
ttxI think I created most of the milestones there12:35
ttxI can go through them once you have numbers12:36
mesteryttx: I am here anytime between now and the top of the hour if you're here, have to run the Neutron meeting at 1400UTC and that will consume me for an hour.13:04
ttxmestery: I'd rather talk to you now, since RC2 discussion usually goes beyond the allocated 10min13:05
ttx#topic Neutron13:05
mesteryThat was my thinking as well13:05
mesteryThanks for being flexible!13:05
ttx#link https://bugs.launchpad.net/neutron/+bugs?field.tag=kilo-rc-potential13:06
ttxThere seems to be enough matter in there to justify a RC2 window now13:06
mestery++13:06
ttxAlso I hapopen to have merged somethign in neutron-fwaas to unblock that branch already13:06
mestery:)13:06
ttxso let me open the milestone and we'll target stuff to it13:06
mesteryAck13:06
ttxWe don't really have a bug for https://review.openstack.org/#/c/175137/13:08
ttx(the one I merged to unblock fwaas)13:08
* mestery looks13:08
mesteryAh13:08
mesteryOK13:08
mesteryShall I file one?13:08
ttxwould be good to have one so that people who want to know the bug diff between RC1 and RC2 can see it13:09
mesteryAck opening one now13:09
ttxWe'll mark it fixed directly13:09
ttxIn the mean time I'll add the 3 criticals to RC213:09
mesteryack13:10
mesteryttx: Bug for the review noted above: https://bugs.launchpad.net/neutron/+bug/144664213:10
openstackLaunchpad bug 1446642 in neutron "Updated Protocol named constants" [Low,Fix committed] - Assigned to Romil Gupta (romilg)13:10
mesteryttx: Handy gerrit query for our potential backports: https://review.openstack.org/#/q/branch:stable/kilo+status:open+(project:openstack/neutron+OR+project:openstack/neutron-fwaas+OR+project:openstack/neutron-lbaas+OR+project:openstack/neutron-vpnaas),n,z13:11
ttxlet's look at the kilo-rc-potential list first, we'll match it with backports after13:12
mesteryAck13:12
ttxhttps://bugs.launchpad.net/neutron/+bug/143804013:12
openstackLaunchpad bug 1438040 in neutron "fdb entries can't be removed when a VM is migrated" [High,Fix committed] - Assigned to Kyle Mestery (mestery)13:12
ttxThis one links to a fix that closes 3 bugs13:12
mesteryYes, it's an efficient fix :)13:12
ttxlooks simple enough and worthy13:13
mesteryYes13:13
ttxI'll target the corresponding three bugs13:13
mesteryThank you!13:13
ttxhttps://bugs.launchpad.net/neutron/+bug/144204313:14
openstackLaunchpad bug 1442043 in neutron "Brocade Vyatta Firewall feature impacted by L3 agent refactor" [High,Fix committed] - Assigned to vishwanath jayaraman (vishwanathj)13:14
mesteryThis one fixes the Brocade Vyatta driver for FWaaS13:15
mesteryIt's low risk and should be in RC213:15
ttxack13:15
ttxhttps://bugs.launchpad.net/neutron/+bug/144379813:16
openstackLaunchpad bug 1443798 in neutron "Restrict netmask of CIDR to avoid DHCP resync" [High,In progress] - Assigned to watanabe.isao (watanabe.isao)13:16
mesteryI'm actually sad this one didn't merge yet13:16
mesteryBut it hasn't passed Jenkins and still has a -1 on it.13:16
ttxok, let's keep it on list and see where it is when we close the window13:17
mesteryYes! The issue with that one is if we don't fix it, we may need to issue a security alert13:17
mesteryI'll highlight this one in the neutron meeting13:17
ttxlast 3 fixcommitted would be:13:17
ttxhttps://bugs.launchpad.net/neutron/+bug/143985713:17
openstackLaunchpad bug 1439857 in neutron kilo "live-migration failure leave the port to BUILD state" [Medium,New]13:17
ttxalready targeted13:17
ttxhttps://bugs.launchpad.net/neutron/+bug/144249413:18
openstackLaunchpad bug 1442494 in neutron "test_add_list_remove_router_on_l3_agent race-y for dvr" [Medium,Fix committed] - Assigned to Swaminathan Vasudevan (swaminathan-vasudevan)13:18
mestery1439857 needs to go in for sure13:18
mesterySame with 144249413:18
ttxack13:18
ttxhttps://bugs.launchpad.net/neutron/+bug/144261513:19
openstackLaunchpad bug 1442615 in neutron "don't ship ml2_conf_odl.ini" [Medium,Fix committed] - Assigned to Ihar Hrachyshka (ihar-hrachyshka)13:19
ttxgood pre-release fix as well13:19
mestery1442615 is pretty simple and will make packager's lives easier13:19
mesteryYes13:19
ttxok, now let's match those with stuff already proposed13:20
ttxrunning through your query13:20
ttxtop to bottom13:20
ttxerr13:21
ttxNot a big fan of open issues like https://bugs.launchpad.net/neutron/+bug/144541213:21
openstackLaunchpad bug 1445412 in neutron "performance of plugin_rpc.get_routers is bad" [High,In progress] - Assigned to Kevin Benton (kevinbenton)13:21
ttxthose tend to never be completed13:21
mesteryI'm not sure why that one is cherry-picked back13:21
mesteryAnd I agree13:21
ttxwhich odes not work well with the release process13:21
ttxIt's one side-effect of naming the branch stable/kilo. People thinnk stable rules apply.13:22
mesteryShall we -2 that for now until we open stable/kilo?13:22
mesteryYes13:22
mestery:)13:22
ttxfungi: ^ see13:22
ttxyes13:22
ttxhttps://review.openstack.org/#/c/175588/13:23
ttxlooks same13:23
mestery-213:23
mesteryThe next two are global requirements13:23
ttxskipping those for the moment13:23
fungittx: what am i looking at? the stable backports to kilo discussion or something else?13:23
ttxfungi: me complaining about the predicted side effects of naming stuff stable/kilo13:23
mesteryAck13:24
* ttx ranting told you so13:24
mesteryttx: This one can go in13:24
mesteryhttps://review.openstack.org/#/c/175385/13:24
ttxyep13:25
ttxskipping translations13:25
ttxhttps://review.openstack.org/#/c/174608/13:25
fungittx: speaking of, did bswartz get up with you about approving changes for stable/kilo in manila?13:25
mesteryttx: I added a +2, are you just going to merge this post our meeting?13:25
ttxNo bug there13:25
ttxfungi: not yet13:25
ttxmestery: I'll approve a bunch yes13:25
mesteryFor 174608, I'll file a bug now13:25
fungihe was confused that release management was taking over manila's release project since it's not part of the integrated release13:25
fungier, taking over manila's release13:26
ttxfungi: right, also unclear if stable branch team will take it as well13:26
fungii didn't know why you had me add it to the list of projects to do branch restrictions on, so told him to check with you13:26
mesteryttx: https://bugs.launchpad.net/neutron/+bug/144665713:27
openstackLaunchpad bug 1446657 in neutron "Add Kilo release milestone" [Medium,In progress] - Assigned to Henry Gessau (gessau)13:27
ttxmestery: so I guess this is necessary as well13:27
mesteryttx: ack, we do this for each release13:27
ttxwe'll have to add the other -aas13:27
ttxis it somethign that needs to land in master as well ?13:28
mesteryttx: I think so too, I'll poke HenryG on that in the Neutron meeting13:28
mesteryNo, it's only in the stable branches13:28
ttxhmm, looks like it did though https://review.openstack.org/#/c/174483/13:29
* mestery looks13:29
mesteryI stand corrected13:29
ttxok, will un-213:29
ttxhttps://review.openstack.org/#/c/175029/ is fine13:30
mesteryack13:30
ttxhttps://review.openstack.org/#/c/174699/13:30
ttxfine too13:31
mesteryYes13:31
ttxThe other two add Kilo milestone are ok too. Could you add a comment to ref the bug number13:31
mesteryThe next two are the milestone commits for vpnaas and lbaas13:31
mesteryYes13:31
ttxhttps://review.openstack.org/#/c/174071/13:32
ttxSounds like a good thing to have too13:32
mesteryBleah, no bug again13:32
mesteryShall I quickly file one and reference it again?13:33
ttxwell we could approve that one as a stable/kilo branch setup thing13:33
mestery:)13:33
ttxI'll approve that one first13:33
mesteryexcellent13:33
ttxif you remove your -213:33
mesterydone13:33
ttxsame for the other two13:33
mesteryDone for all 313:34
ttxhttps://review.openstack.org/#/c/174641/13:34
ttxtargeted, so ok13:34
mesteryyup13:35
ttxhttps://review.openstack.org/#/c/174373/13:35
ttxso that one closes 3 bugs only one of which is targeted13:35
mesteryYes, I see that. Shall I target the other two? This is something we want in RC2.13:36
ttxI fear we might miss part of the bugfixes there, since there are related merges as well13:36
mesteryI was going on what HenryG told me on this one, in that getting this particular commit in would be great to have13:36
mesteryI can talk to him again and verify13:36
ttxwow, this is a mess, there is a revert in there13:37
mesteryActually13:37
mesteryYes13:37
mesteryI think we need this one, this fixed a bunch of issues on subnet allocation which caused us gate issues recenttly13:37
mesteryhttps://bugs.launchpad.net/neutron/+bug/144018313:37
openstackLaunchpad bug 1440183 in neutron kilo "DBDeadlock on subnet allocation" [Critical,New]13:37
mesteryThat was the nasty gate bug13:37
ttxwe targeted this one already13:38
mesteryYes13:38
ttxso I'm a bit confused13:38
ttxwant to make sure we don't lose partn of the commit history that made thi spatch necessary13:39
mesteryI agree13:39
ttxhmm, so there was one fix, which was reverted, then a new one13:40
ttxonly the new one was proposed to stable13:40
ttxjust need to make sure we don't need the first part at all13:40
mesteryThe revert is in stable/kilo: 0107bdd5f03e3d0fef6be88b8b586f735f61052213:40
mesteryThat's the commit hash13:40
ttxhmm, ok, probably safe if it applies anyway13:41
mesteryYes, it shoudl be ok13:41
mesteryI just verified the revert is in stable/kilo13:41
ttxso this one really closes those 3 bugs for us ? I'll target them as well13:41
mesteryYes, it does.13:41
mesteryAnd thanks for targeting them13:41
ttxhttps://review.openstack.org/#/c/174610/13:42
ttxsame, add a comment on that bug for reference13:42
ttxhttps://review.openstack.org/#/c/174057/ is targeted alright13:43
mesterydone and yes13:43
ttxsame for last one13:43
mesteryyes13:44
ttxOK, I'll map to the ones which have fix proposed now13:44
mesteryThanks!13:44
ttxso we know if anything is missing13:44
ttxmestery: we need that one in asap : https://review.openstack.org/#/c/174498/13:47
ttxnot in master so can't land in stable/kilo13:47
mesteryGood catch! Just put it in the merge queue13:47
mesteryThe queue is small, hopefully it lands in it's estimated 54 minutes13:48
ttxOK, looks like all the backports were proposed: https://launchpad.net/neutron/+milestone/kilo-rc213:49
mesteryYay! :013:49
ttxI'll push the W+1 button for them later13:50
ttxin the mean time we can send rechecks where needed13:50
mesteryYes13:50
mesteryI put +2s on most of those in preparation for you13:50
mesteryIs the branch still limited with who can approve there?13:50
ttxit's limited to neutron-milestone and release managers I think13:51
ttxuntil release where it will go under control of the stable maint team13:51
mesteryExcellent13:51
mesteryYes13:51
ttxOK, I think we are good13:51
mesteryOK, thanks for all the help here! I'm glad I pinged you early today :)13:51
ttxHopefully we'll be able to close eth RC2 window tomorrow or Thursday13:51
mesteryyes13:51
* mestery goes off to prep for neutron meeting13:52
ttxonce we straighten out the requirements situation13:52
mestery++13:52
mesteryOh one more thing13:52
mesteryI need to talk to you or dhellmann about the branchign strategy for python-neutronclient13:52
mesteryBut that can wait until the RC2 stuff is done13:52
ttxack13:52
mesteryJust putting it on yoru radar for now13:52
mesterycool13:52
mesteryOK, have a great day ttx!13:52
ttxcheers13:52
ttxnikhil_k: ohai14:21
nikhil_khehey14:21
ttx#topic Glance14:21
ttxhttps://bugs.launchpad.net/glance/+bugs?field.tag=kilo-rc-potential14:21
ttxNot that many fixcommitted things in there14:22
ttxhttps://bugs.launchpad.net/glance/+bug/143457814:22
openstackLaunchpad bug 1434578 in Glance "Inefficient db call while doing a image_get with image_id." [Low,Fix committed] - Assigned to Kamil Rykowski (kamil-rykowski)14:22
nikhil_kttx: yes, let's not look at that14:22
nikhil_kttx: here's what I've for RC2 blockers https://trello.com/c/CoZ9g13d/45-kilo-rc214:22
ttxok looking14:23
ttxhttps://bugs.launchpad.net/glance/+bug/144502614:23
openstackLaunchpad bug 1445026 in Glance "glance-manage db load_metadefs does not load tags correctly" [Critical,In progress] - Assigned to Pawel Koniszewski (pawel-koniszewski)14:23
*** thingee has joined #openstack-relmgr-office14:23
ttxthat one is not fixed in master yet14:23
ttxso you should get it merged asap if you want it under consideration for a RC214:24
nikhil_kyes14:24
ttxhttps://review.openstack.org/#/c/173646/14:24
ttxIf we want that one, we'll need a bug for it + get it merged to master asap14:25
ttxhttps://review.openstack.org/#/c/169813/14:25
ttxneeds to merge in master too14:25
nikhil_kok14:25
ttxsame for https://bugs.launchpad.net/glance/+bug/143687714:25
openstackLaunchpad bug 1436877 in Glance "metadef JSON files need updating for the Kilo release" [Medium,In progress] - Assigned to Wayne (wayne-okuma)14:25
ttxso basically, you'll need those merged in master by tomorrow so we can open a RC2 window with them in14:26
ttxno need to backport right now, priority on getting them in master branch14:26
nikhil_kttx: can we sync on thursday instead?14:26
ttx#info Glance RC2 potentials stored at https://trello.com/c/CoZ9g13d/45-kilo-rc214:26
nikhil_ktomorrow might be tricky because of timezone issues14:26
ttxnikhil_k: sounds good14:26
nikhil_kthanks14:26
ttxnote we have one already proposed14:27
nikhil_kttx: I have a meeting conflicting at this time on thursday so, may be an hours later then14:27
nikhil_kttx: proposed? what exactly?14:27
ttxhttps://review.openstack.org/#/c/175442/ (partial backport for https://bugs.launchpad.net/glance/+bug/1445827)14:27
openstackLaunchpad bug 1445827 in Glance "unit test failures: Glance insist on ordereddict" [High,In progress] - Assigned to Stuart McLaren (stuart-mclaren)14:27
nikhil_kah ok14:27
ttxI'll blkock it until Thursday14:27
nikhil_kcool14:28
ttxthe other topic is the glanceclient 0.17.1 update. We should be able to push it tomorrow or thursday14:28
ttxonce the lib requirement mess is solved14:28
nikhil_kcool14:28
ttxwe'll need that one out asap so we can bump the requirements to >=0.17.114:29
nikhil_kttx: hmm, sure. Thursday again then?14:29
ttxotherwise it won't make it to ceilometer cinder heat horizon ironic nova RC2s14:29
ttxnikhil_k: soudns good14:29
nikhil_kI will try to get reviews on it today/tomorrow14:29
nikhil_kthanks14:29
ttxwill talk to you then. In the mean time, get those fixes in master14:30
nikhil_kyup14:30
ttxcheers!14:30
nikhil_kSanté (hope I used that correctly)14:31
ttxthingee: around?14:31
thingeettx: hi!14:31
ttx#topic Cinder14:31
ttxhttps://bugs.launchpad.net/cinder/+bugs?field.tag=kilo-rc-potential14:31
ttxthingee: looks like we ahve enough material to do a RC2 now14:32
thingeeyeah 1446583 is new to me. I just woke up :)14:32
thingeethat critical one14:32
ttxLet's start with reviewing kilo-rc-potential bugs, then we'll look at the proposed backports14:32
ttxsome solo-incubator code you fall victim of14:33
ttxlet's leave that one out of the equation for now14:33
ttxhttps://bugs.launchpad.net/cinder/+bug/143937114:33
openstackLaunchpad bug 1439371 in Cinder "Volume creation from image fails for UEC and Glance API version 2" [High,Fix committed] - Assigned to Jon Bernard (jbernard)14:33
ttxsounds like a good one14:34
thingeeyeah14:34
ttxok, targeting14:34
thingeeI left a +114:34
ttxhttps://bugs.launchpad.net/cinder/+bug/144333114:35
openstackLaunchpad bug 1443331 in Cinder "Fix a wrong argument of create method in QoSSpecsController Class" [High,Fix committed] - Assigned to Daisuke Fujita (fuzita-daisuke)14:35
thingeeI'll need to propose one14:35
ttxsounds pretty straightforward14:35
thingeepretty good catch14:35
ttxhttps://bugs.launchpad.net/cinder/+bug/140670314:36
openstackLaunchpad bug 1406703 in Cinder "Deleting VM with an attached volume during copy-volume-to-image causes the volume remains in-use state" [Medium,Fix committed] - Assigned to Abhijeet Malawade (abhijeet-malawade)14:36
ttxadd new db api? Is that safe ?14:37
thingeehttps://review.openstack.org/17589814:37
ttxlike, doesn't it have to be used by drivers or anything ?14:37
thingeenah it's only touched by the manager14:38
thingeethe manager is the only layer that can make state changes for drivers.14:38
ttxyou want it in RC2 ?14:38
thingeeyes14:39
ttxok adding14:39
ttxhttps://bugs.launchpad.net/cinder/+bug/143729014:39
openstackLaunchpad bug 1437290 in Cinder "Windows SMBFS: volume extend fails" [Undecided,Fix committed] - Assigned to Petrut Lucian (petrutlucian94)14:39
thingeelimited to a driver. I'm not worried14:40
ttxpretty simple14:40
ttxadding14:40
ttxok...14:41
ttxLet's map that to proposed fixes @ https://review.openstack.org/#/q/project:openstack/cinder+branch:stable/kilo,n,z14:41
thingeehttps://review.openstack.org/17590014:41
ttxhttps://review.openstack.org/#/c/174050/ is for https://bugs.launchpad.net/cinder/+bug/1439371 which we targeted14:41
openstackLaunchpad bug 1439371 in Cinder kilo "Volume creation from image fails for UEC and Glance API version 2" [High,In progress]14:41
ttxhttps://review.openstack.org/#/c/175723/14:42
ttxmaps to https://bugs.launchpad.net/cinder/+bug/1444855 (not targeted)14:42
openstackLaunchpad bug 1444855 in Cinder "RBD driver doesn't support customized ceph cluster name" [Low,Fix committed] - Assigned to Huang Zhiteng (zhiteng-huang)14:42
ttxwhat should we do with that one14:42
ttxadding a config option, beh14:43
thingeeyeah not good14:43
ttxI .. think we are a bit late for that14:43
thingeeagreed14:43
ttxI'll let you -2 it14:43
ttxhttps://review.openstack.org/#/c/175740/14:44
ttxmaps to targeted bug14:44
ttxhttps://review.openstack.org/#/c/174482/14:44
ttxarh14:45
ttxdamn fix was pushed to stable/juno14:45
thingeewhich?14:46
ttxhttps://review.openstack.org/#/c/174700/14:46
thingeewe can revert14:46
ttxyes, sounds like a good idea14:46
ttxhttps://review.openstack.org/#/c/175261/ -> https://bugs.launchpad.net/cinder/+bug/144556114:48
openstackLaunchpad bug 1445561 in Cinder "cinder scheduler fails to handle CONF.scheduler_max_attempts = 1 " [Medium,Fix committed] - Assigned to Huang Zhiteng (zhiteng-huang)14:48
ttxhmm, new log message... not sure the bug is worth it14:49
ttxalso seems to have regression potential14:49
thingeehttps://review.openstack.org/17590914:50
thingeeI agree14:51
thingeeI'll give it a -214:51
thingee-1 rather. Don't have -2 abilitieis14:52
ttxhttps://review.openstack.org/#/c/175202/ -> https://bugs.launchpad.net/cinder/+bug/141010714:52
openstackLaunchpad bug 1410107 in Cinder "NetApp lun misaligned on hyper-v" [Undecided,Fix committed] - Assigned to Bob Callaway (bob-callaway)14:52
ttxwe should fix that14:52
* ttx looks14:52
ttxthingee: you appear not to be in https://review.openstack.org/#/admin/groups/82,members14:53
ttxbut I have powerz to add you! cool14:54
thingeeha even jesse has abilities :)14:54
ttxwill clean up14:54
ttxok done14:54
ttxso what about this LUN thing14:54
thingeedone14:55
ttxfeels like a rather large patch, but limited in scope14:55
ttxI'm fine with it if you want it...14:55
ttxbut it's definietly larger than what we ususally accept at this stage14:56
* thingee reads things closer14:56
thingeethis is an optimization for other hypervisiors14:57
thingeenot concerned this needs to go in right now14:57
thingee"NetApp luns need to be aligned properly while attaching it to different operating systems. Currently its optimized for linux but will eventually need to cater to openstack environments with multiple hypervisors and guest os's."14:57
thingeeaccording to the bug description anyways14:57
ttxok, let's keep it out14:58
ttxhttps://review.openstack.org/#/c/174051/ -> https://bugs.launchpad.net/cinder/+bug/144422414:58
openstackLaunchpad bug 1444224 in Cinder "Race in PureISCSIDriver when creating hosts" [Undecided,Fix committed] - Assigned to Patrick East (patrick-east)14:58
ttxnot targeted yet14:58
ttxsounds safe and simple14:59
thingeeagreed I'm fine with it14:59
ttxoka dding14:59
ttxhttps://review.openstack.org/#/c/174052/14:59
ttx-> https://bugs.launchpad.net/cinder/+bug/143297215:00
openstackLaunchpad bug 1432972 in Cinder "update quota failed with multi-value in one request" [High,Fix committed] - Assigned to Ankit Agrawal (ankitagrawal)15:00
ttxyour call, I'm fine with it15:00
thingeeyeah I'm fine with this15:01
thingeetested it myself15:01
ttxok targeting15:01
ttxhttps://launchpad.net/cinder/+milestone/kilo-rc215:01
ttxresult ^15:01
thingeethank you15:02
ttxWe'll get that in and prepare to close on Wed/Thu15:02
ttxneed to run15:02
thingeeI'll go through my -1's and switch them to -2's when I get back. Gotta head out.15:02
thingeeok, thanks!15:02
ttxdavid-lyle: Having a call now, will ping you later15:02
*** mestery has quit IRC15:11
*** mestery has joined #openstack-relmgr-office15:12
*** eglynn has quit IRC15:24
ttxdavid-lyle: available now if you are around15:28
*** david-lyle has quit IRC15:36
devanandattx: i'm here if you're free now15:46
ttxdevananda: well, hmm... about to talk to morgan and his window of availability is short15:46
ttxso would rather talk to you in a few :)15:47
devanandak k15:47
morganfainbergo/15:47
ttxmorganfainberg: ohai15:47
ttx#topic Keystone15:47
morganfainberg:)15:47
devanandaI'll be afk for ~15. see you at our normal time15:47
ttxWe have a RC2 window opened15:47
morganfainbergyes we do15:47
ttxhttps://launchpad.net/keystone/+milestone/kilo-rc215:48
ttxanything new to push onto it ?15:48
morganfainbergand all outstanding fixes besides what was discussed in #openstack-oslo this morning look to be committed15:48
ttxright15:48
morganfainberglet me look at the rc potentials... but i don't think anything else warrants being added15:48
ttxI'll remove from potentialks the ones already atrgeted for sanity15:49
morganfainbergyep15:49
morganfainberglooks like we don't have any more i see needing to be targeted to rc15:49
morganfainbergexcept the in-progress one from this morning15:50
morganfainbergwhihc i see was added15:50
ttxright, so let's talk about libraries15:50
ttxWe'll ned a keystoneclient and a keystonemiddleware stable/kilo .Z bump15:50
ttxto include that security fix15:50
ttxI.. am not sure we want a bump the minimum version in requirements though15:51
ttxas that would cascade-affect to everyone and that is nasty15:51
morganfainbergdidn't we fix the .Z requirement?15:51
morganfainbergsince we couldn't land anything in keystoneclient15:51
ttxthat is a different issue15:51
morganfainbergoh minimum15:52
ttxthe question is, after you release keystoneclient 1.3.1 and keystonemiddleware 1.5.115:52
morganfainbergoh uh, we have an OSSN out right?15:52
ttxshould we set >=1.3.1 and >=1.5.1 in global-reqs15:52
ttxyes we do15:52
morganfainbergi think i'm ok with leaving it as is.15:52
morganfainbergfor sanity sake15:52
ttxsounds good15:53
ttxso we can't release until dhellmann is finished with releasing an uncapped liberty library for everything15:53
morganfainbergright15:53
ttxotherwise it breaks the world15:53
ttxso hopefully that will be completed later today15:54
ttxand we'll able to do those point updates stable/kilo libs tomorrow15:54
morganfainbergsounds good15:54
ttxand then merge the last bumps and close the RC2 for keystone15:54
ttxI'd say Thursday at the latest, maybe tomorrow.15:54
morganfainbergwfm15:54
ttxall depends on that oslo-incub thing too15:55
ttxso I'll ping you again tomorrow.15:55
morganfainbergright. lets hope that solves it. but this is another reason i am happy eventlet is going away15:55
morganfainbergfor keystone15:55
morganfainbergi wish i could remove it in liberty15:55
morganfainberginstead of M15:55
ttxdamn users15:55
morganfainbergright!? ;)15:55
ttxAnyway, that is all I had15:56
morganfainbergoh, keystoneauth15:56
ttxYou can see the design summit layout, which is pretty fragmented for keystone (by design)15:56
morganfainbergadded the goverance change and chasing down infra changes.15:56
ttxso that you don't blatantly overlap with anyone in particular15:56
ttxkeystoneauth?15:57
morganfainberglib that isolates session/auth plugins, etc15:57
ttxliberty stuf right15:57
morganfainbergso to auth with keystone you don't need to forklift in all of keystoneclient15:57
morganfainbergyeah15:57
morganfainbergjust a heads up the changes are pending.15:57
ttxok, so I'll gladly ignore that for now15:57
morganfainberghah15:57
morganfainbergok i'll look at the design summit layout for keystone15:58
* ttx 's brain already divided in 15 projects RCs right now15:58
morganfainbergonly 15?!15:58
morganfainbergphsaw,15:58
ttx16 actually.15:58
ttxI can't count anymore15:58
morganfainbergoh now thats the staw that breaks the camel's back.15:58
morganfainberg15 easy, 16... too much :P15:59
morganfainberganyway, all sounds good.15:59
ttxyep, always the 16th that creates the most problems15:59
ttxmorganfainberg: ok, ttyl15:59
ttxnotmyname: ready when you are15:59
notmynamehello15:59
ttx#topic Swift15:59
ttxhttps://launchpad.net/swift/+milestone/2.3.0-rc215:59
ttxI added a bug to track that PyEClib thing16:00
notmynameah ok16:00
notmynameI'll be adding the rest today16:00
ttxthat way I know what I'm blocking on16:00
ttxanything else to expect ?16:00
ttxhttps://review.openstack.org/#/q/project:openstack/swift+branch:stable/kilo,n,z16:00
notmynamewe've got a list of the stuff that needs to be in rc2, and I'm shooting for a commit SHA by EoD for it16:00
ttxhas https://review.openstack.org/#/c/174552/16:00
ttxI assumed https://review.openstack.org/#/c/175741/ is part of that ECLib bump ?16:01
notmynamehttps://wiki.openstack.org/wiki/Swift/PriorityReviews16:01
ttxIf I assumed too much, I can divide that bug I created into two16:01
notmynamehmm...I'm just now catching up from what happened while I was asleep16:02
*** david-lyle has joined #openstack-relmgr-office16:02
notmynamelooks like patches have landed and there are stable/kilo patches16:02
notmynameI was hoping to do that myself16:02
ttxthat wiki matches what is up on https://review.openstack.org/#/q/project:openstack/swift+branch:stable/kilo,n,z16:02
ttxI'll let you do that then16:02
notmynameanyway, today, I'll be making sure they have RC2 bugs, reproposing, and landing them on stable/kilo16:02
notmynamebut it looks like we've got all the patches needed on master16:03
ttxok. Just make double-sure anything you merge in stable/kilo is already landed in master16:03
notmynameof course :-)16:03
ttxOK, planning to cut RC2 for you tomorrow morning16:04
notmynameI'll send an email with the commit sha as soon as I have it16:04
ttxanything else to mention?16:04
notmynameno, I think I'm good. later this week I'll be refocusing on summit planning. if I have questions, I'll ping you then16:04
notmynamethanks for the help with global requirements16:04
david-lylettx: here if you have time16:05
ttxnotmyname: alright then16:05
ttxdavid-lyle: let's do it real quick16:05
ttx#topic Horizon16:05
ttxhttps://bugs.launchpad.net/horizon/+bugs?field.tag=kilo-rc-potential16:06
ttx2 candidates there16:06
ttxI think we can open the RC2 now and merge what you have proposed... or would you rather wait a bit more ?16:06
david-lyleyes and two others that are in progress may land16:06
david-lylewe are waiting on the final translations I believe16:07
david-lyleApril 23 is the expected date16:07
ttxhmm, so how about we open the RC2 tomorrow ?16:07
david-lylethat sounds good16:07
ttxso that we don't keep the thing untestable for too long16:07
ttxsounds good, lets me catch my breath16:07
david-lyleI'll try to bump the other two in progress bugs along16:08
ttxright, and anything else that is fixed on master could be included if safe16:08
ttxso maybe time to give the last ones a bump16:08
ttxI'll talk to you tomorrow then16:08
david-lylesounds good16:08
david-lylethanks16:09
ttxnp! thanks16:09
ttxdevananda: you're on16:09
devanandattx: o/16:09
ttx#topic Ironic16:09
ttxhttps://bugs.launchpad.net/ironic/+bugs?field.tag=kilo-rc-potential16:09
ttxis pretty empty but I suspect you have your own list16:09
devananda3 candidates16:09
devanandaone has landed on master already, the other two should be landable soon16:10
ttxhmm, so I'd say we should wait at least one more day to open the RC2 window16:10
ttxespecially if you want those fixes in16:10
devanandacould you explain / point me t oa reference for this process? it seems different from last cycle, and I haven't figured it out yet16:10
ttxI'd rather only consider for backport stuff that is already fixed in amster16:11
devanandalike, when we can land backports16:11
ttxdevananda: I think last cycles you were not integrated yet16:11
ttxso you were pretty much deciding16:11
ttxhere the idea is to encourage testing16:11
devanandaindeed. but we were trying to track the release process as closely as possible16:11
ttxpeople are dumb, they only test when they believe it will be the final thing16:11
devanandaheh16:12
ttxso whenever you say something like "we'll do a RC2 two days before release" they wait16:12
ttxhuman nat ure I guess16:12
ttxso you don't say that16:12
ttxYou say "this RC1 will be final ! test it!"16:12
devanandagotcha. so "open rc2" really means "tag rc2"16:12
ttxthen when you finally decide to do a RC2, you want the window to be as short as possible16:12
ttxand get them back to testing16:12
devanandaand we stage the fixes as proposed to kilo/stable but with a -2 until then16:12
devananda?16:13
ttxAlso reduces risk that you would keep a RC window opened over release time16:13
ttxi.e. you don't open something you don't know how to close16:13
ttxhence, ideally,  the targeting of only-already-fixed-in-master things16:13
devanandaright. quite a different process from the other milestones, and I hadn't read anything about this previously16:13
devanandarelatedly, what about fixes for the stable branch of the client?16:14
ttxhttps://wiki.openstack.org/wiki/ReleaseCycle#Pre-release_.28Release_Candidates_dance.2916:14
ttxso that is slightly different16:14
devanandayea, that ^ does not describe what we're doing16:14
ttxAnd again, using the same branch name is confusing16:14
devananda"A new milestone will be open (RC2), with bugs targeted to it. " << not what we're doing16:14
ttxwhat we'll be doing16:15
devanandaI think that is where my confusion stemmed from. thanks for clarifying16:15
ttxso stable/kilo for openstack/ironic is a pre-release branch at the moment16:15
ttxbut for the lib, it's a real stable branch16:15
devanandahmm. k.16:15
ttxThey have different meanings, which is why I resisted them being called the same thing16:16
ttxBut then sdague won16:16
devanandahe does that some times16:16
ttxso the real stable branch is something you push backport of fixes too16:16
ttxno need for RC windows. No deliverable to test, no release candidates16:16
devanandacool16:17
ttxno coordinated release either16:17
devanandai'll do the usual things there, then16:17
ttxthat said... stable branches for libs are there for testing purposes16:17
ttxso only very critical fixes should be backported to them16:17
ttxyou are still supposed to give users the HEAD version and be backward compatible16:17
devanandafwiw, people are already beginning to ask about stable branches of libs & clients and asking why we're not just calling it the kilo release of python-ironicclient16:17
ttxIt's more "the version the rest of Kilo was tested with"16:18
devanandaI understand the reasons that we want them for testing purposes, but it's going to confuse users16:18
ttxYou can point them to http://specs.openstack.org/openstack/openstack-specs/specs/library-stable-branches.html16:19
devanandawill do16:19
ttxbut yeah, i agree this is confusing16:19
ttxanyway16:19
ttxback to topic16:19
devananda:)16:19
ttxSo I propose we discuss the opening of the RC2 window tomorrow16:19
ttxhopefuly those fixes will have landed and we'll have a peaceful conversation16:20
devananda:)16:20
* ttx doesn't like unfixed bugs in his RC lists16:20
devanandasounds good. same bat time, same bat channel?16:20
ttxyes, just ping me when you can talk16:21
ttxcould be before16:21
ttx#topic Trove16:21
ttxNo SlickNik today, looking into opening a RC2 window there on Thursday to catch late requirements/translations16:21
ttx#endmeeting16:21
openstackMeeting ended Tue Apr 21 16:21:49 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:21
openstackMinutes:        http://eavesdrop.openstack.org/meetings/ptl_sync/2015/ptl_sync.2015-04-21-08.02.html16:21
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/ptl_sync/2015/ptl_sync.2015-04-21-08.02.txt16:21
openstackLog:            http://eavesdrop.openstack.org/meetings/ptl_sync/2015/ptl_sync.2015-04-21-08.02.log.html16:21
*** david-lyle has quit IRC17:08
notmynamettx: so translation updates are a "thing" that should just land? eg https://review.openstack.org/#/c/175324/17:11
notmynameon stable/kilo17:11
*** notmyname has quit IRC18:16
*** johnthetubaguy is now known as zz_johnthetubagu18:16
*** notmyname has joined #openstack-relmgr-office18:17
*** david-lyle has joined #openstack-relmgr-office18:39
*** david-ly_ has joined #openstack-relmgr-office18:46
*** david-lyle has quit IRC18:46
Kiallnotmyname: I had that same question.. thierry can you mention me when you reply so I see it? :)19:11
notmynameKiall: ttx: I landed it :-)19:11
notmynameKiall: see the comment from Andreas on it https://review.openstack.org/#/c/175324/19:11
KiallAh, I see.. perfect :)19:12
*** david-ly_ has quit IRC19:18
ttxKiall, notmyname: yeah, basically19:36
dhellmannttx, sdague, fungi: the master versions of the libs are released, so the next step is to revert the change to ignore requirements in those repos -- submitted as https://review.openstack.org/#/c/176036/19:45
* ttx looks19:46
ttxthere may be more to revert.. fungi ?19:47
funginot sure--i'm chairing the infra meeting for a few more minutes19:49
ttxchecking myself19:49
ttxno, the other I was thinking of is actually about jobs that did not make sense on stable/kilo, so unrelated19:50
sdagueright, we're still at a gap on stable kilo support as well until we can resolve the keystone / oslo issue19:55
*** david-lyle has joined #openstack-relmgr-office20:21
SlickNikttx: we found https://bugs.launchpad.net/trove/+bug/1446735 in Trove which we need to get into the next kilo-RC20:40
openstackLaunchpad bug 1446735 in Trove "MongoDB guest won't start" [High,Confirmed] - Assigned to Doug Shelley (0-doug)20:40
SlickNikworking on the fix in master and hope to land it shortly.20:41
ttxSlickNik: OK, let's discuss a RC2 tomorrow20:46
notmynamettx: FYI, all RC2 patches in swift seem to be blocked by grenade. I'm told https://bugs.launchpad.net/oslo-incubator/+bug/1446583 is the issue20:55
openstackLaunchpad bug 1446583 in Keystone "services no longer reliably stop in stable/kilo" [Critical,In progress] - Assigned to Julien Danjou (jdanjou)20:55
ttxnotmyname: err, weird, the .gitreview one passed20:59
notmynameyeah. clarkb says it might be transient. I rechecked them20:59
ttxI guess we didn't have grenade on back then20:59
notmynamebut I wanted to give you a head's up asap.20:59
ttxnotmyname: yes, we ned to squish that bug there20:59
notmynamethose are the patches we need in rc2. all validated locally. just need to get jenkins to land them (that's all we're waiting on)21:00
ttxok21:00
fungidhellmann: ttx: yeah the https://review.openstack.org/176036 revert is not the only one. we also need to revert the one which temporarily stopped running requirements check on master for those repos (which wound up being a couple of patches in total once we realized we missed a couple)21:01
fungioh, wait, that was the one21:01
sdaguenotmyname: https://bugs.launchpad.net/oslo-incubator/+bug/1446583 isn't blocking anything except correct testing21:01
openstackLaunchpad bug 1446583 in Keystone "services no longer reliably stop in stable/kilo" [Critical,In progress] - Assigned to Julien Danjou (jdanjou)21:01
fungithe other one was the one to the reqs repo--checking on it now21:01
sdaguethe grenade block is requirements wedging21:02
dhellmannfungi: yeah, I was going step by step but I guess some of these can be done in parallel21:02
notmynamesdague: ok. when I asked how to find the root cause, I was told that was the issue21:02
notmynameif you have pointers on how to track down the real error in a few hundred thousand lines of text, I'd love to know21:02
sdaguenotmyname: whoever told you was wrong :)21:02
fungiclarkb probably thought it was the keystone start/stop bug21:03
notmynameyeah21:03
sdaguegot to a log file - http://logs.openstack.org/12/176012/1/check/check-grenade-dsvm/ab2f02e/logs/grenade.sh.txt.gz21:03
sdaguehit end21:03
sdaguework backwards21:03
sdaguehttp://logs.openstack.org/12/176012/1/check/check-grenade-dsvm/ab2f02e/logs/grenade.sh.txt.gz#_2015-04-21_17_52_55_13721:03
sdague2015-04-21 17:52:55.137 | ERROR: openstackclient.shell Exception raised: (stevedore 1.2.0 (/usr/local/lib/python2.7/dist-packages), Requirement.parse('stevedore>=1.3.0'), set(['cliff']))21:03
*** zz_johnthetubagu is now known as johnthetubaguy21:04
sdaguethe library flush broke stable/juno21:04
ttxsdague: oh. Hm21:04
ttxOnce this mess will be over we'll have to rethink how to make it work in one go21:05
dhellmannttx: I think part of the problem here is we don't have stable branches for clients for juno, right?21:05
dhellmannso juno is installing clients from master?21:06
sdaguedhellmann: the clients are being installed from pypi21:06
sdaguebranches are not relevant in this case21:06
dhellmannso how is stable/juno picking up newer versions of things? have we found which one doesn't have the cap set?21:06
sdaguehttp://logs.openstack.org/12/176012/1/check/check-grenade-dsvm/ab2f02e/logs/grenade.sh.txt.gz#_2015-04-21_17_49_44_96121:07
sdaguewhich gives us - http://logs.openstack.org/12/176012/1/check/check-grenade-dsvm/ab2f02e/logs/grenade.sh.txt.gz#_2015-04-21_17_49_46_34021:07
sdaguecinder -> python-barbicanclient 3.0.1 -> cliff 0.11.0 (uncapped)21:08
dhellmannsdague: barbicanclient appears to be capped, what am I missing?21:08
dhellmannah21:08
sdagueuncapped cliff drags in new stevedor21:08
dhellmannok21:09
dhellmannso this means that having libs uncapped in the future will continue to cause this problem, so that does away with the plan we had of not capping libs21:09
dhellmannthat is, not capping the dependencies libs have21:09
dhellmanncan we add cliff to cinder's dependency list, before barbicanclient, and include a cap there?21:10
dhellmannsdague: ^^21:10
sdaguemaybe? but I have to actually go deal with dinner for the family now.21:11
dhellmannI'll give that a try21:11
sdaguethe explosion is coming in openstackclient, I'd almost venture that the right thing to do is force the versions there21:13
dhellmannsdague: openstackclient is reporting them, but barbicanclient was being installed as part of cinder21:15
dhellmannsdague: see https://review.openstack.org/17608221:18
sdaguedhellmann: sure, but openstackclient could force downgrade on it's install21:19
dhellmannsdague: we could do that, too, I suppose21:19
dhellmannis the problem with osc, or a plugin that osc is loading?21:19
sdaguedhellmann: I don't know21:19
ttxIf this breaks the stable/kilo world, I'm all for a quick patch21:27
ttxsince I have RC2s lined up21:27
ttxdhellmann: I'll go to bed as soon as I'm finished with the meeting, so I won't be able to sanity-check your ideas to fix this. Maybe fungi can help a bit21:32
dhellmannttx: ok, dtroyer is also looking at it21:33
ttxwhere is it discussed ? Let's regroup :)21:34
fungiyeah, i was starting to poke at the unfreeze master reqs revert changes, but if there's still stable issues then maybe that should wait lest we complicate it further21:35
dhellmannttx: #openstack-qa21:40
dhellmannfungi: ^^21:40
*** johnthetubaguy is now known as zz_johnthetubagu21:58

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