Wednesday, 2017-03-15

*** armax has quit IRC00:10
*** hoangcx has joined #openstack-requirements00:39
*** ihrachys has joined #openstack-requirements00:48
*** ihrachys_ has joined #openstack-requirements00:50
*** armax has joined #openstack-requirements00:51
*** ihrachys has quit IRC00:54
tonyblbragstad: It's because https://review.openstack.org/#/c/439973/ also needs to be backported and I haven't done it yet :(01:31
tonybdhellmann, lbragstad: I think we need the cap in stable/* and once we work though the "bad old days" of bumps and re-releases I think we'll be okay01:37
* tonyb is readign scrollback after public-holiday and virus :(01:39
prometheanfiretonyb: woo virus01:44
tonybprometheanfire: nothign terrible just a head full'o'cotton wool01:45
prometheanfireah01:46
*** ihrachys_ has quit IRC02:38
prometheanfiremeetings are 5 central now, nice :D03:32
*** ihrachys has joined #openstack-requirements03:36
*** ihrachys has quit IRC03:46
*** karthikpr has joined #openstack-requirements04:15
openstackgerritMerged openstack/requirements master: Add betamax-matchers to global-requirements  https://review.openstack.org/44323104:16
*** udesale has joined #openstack-requirements04:18
openstackgerritMerged openstack/requirements master: update constraint for oslo.i18n to new release 3.14.0  https://review.openstack.org/44500804:21
*** ihrachys has joined #openstack-requirements04:24
*** karthikpr has quit IRC04:30
*** karthikpr has joined #openstack-requirements04:30
*** karthikpr has quit IRC04:37
openstackgerritMerged openstack/requirements master: Bump oslo.messaging to 5.19  https://review.openstack.org/44530204:45
*** ihrachys has quit IRC05:06
*** karthikpr has joined #openstack-requirements05:10
*** karthikpr has quit IRC05:16
*** karthikpr has joined #openstack-requirements05:17
*** udesale__ has joined #openstack-requirements05:17
*** udesale has quit IRC05:21
*** karthikpr has quit IRC05:21
*** udesale has joined #openstack-requirements05:35
*** udesale__ has quit IRC05:37
*** udesale__ has joined #openstack-requirements05:44
*** udesale has quit IRC05:46
*** armax has quit IRC06:20
tonybSo I've been sick and I'm not feelign up to a late night tonight so I think I'm going to bail on the meeting.  Sorry all.07:48
tonybOf course you're free to have one without me.07:48
*** udesale has joined #openstack-requirements08:13
*** udesale__ has quit IRC08:14
*** amoralej|off is now known as amoralej08:37
openstackgerritOpenStack Proposal Bot proposed openstack/requirements master: Updated from generate-constraints  https://review.openstack.org/44477308:38
*** jpich has joined #openstack-requirements08:39
*** udesale__ has joined #openstack-requirements09:04
*** udesale has quit IRC09:06
amoralejtonyb, question about https://review.openstack.org/#/c/442913/09:09
*** amoralej has quit IRC09:54
*** amoralej has joined #openstack-requirements10:00
dirktonyb: ah, thanks for the update10:05
dirkprometheanfire: do you want to do a meeting? and if so, in which timezone? :)10:05
prometheanfiredirk: I want to go back to bed :P10:06
dirkprometheanfire: do so :)10:06
* dirk doesn't mind10:06
prometheanfirek, back to bed :D10:08
*** udesale has joined #openstack-requirements10:14
*** udesale has quit IRC10:16
*** udesale has joined #openstack-requirements10:16
*** udesale__ has quit IRC10:17
*** openstackgerrit has quit IRC10:18
*** sdague has joined #openstack-requirements10:27
*** udesale has quit IRC10:41
*** hoangcx has quit IRC10:46
*** kornicameister has quit IRC12:09
*** openstackgerrit has joined #openstack-requirements12:14
openstackgerritSaad Zaher proposed openstack/requirements master: update global requirements constraint for python-freezerclient to new release 1.3.0  https://review.openstack.org/44590512:14
openstackgerritMerged openstack/requirements master: Allow newer SQLAlchemy  https://review.openstack.org/42319212:26
*** jpich has quit IRC12:46
*** jpich_ has joined #openstack-requirements12:46
*** jpich_ is now known as jpich12:51
*** amoralej is now known as amoralej|lunch13:34
*** udesale has joined #openstack-requirements13:59
dhellmanntonyb, lbragstad : I'm happy to keep the cap for now, if it's working out ok.14:00
prometheanfireupgrades seem to be doing alright14:01
lbragstaddhellmann is this change alright then? https://review.openstack.org/#/c/439355/6/requirements.txt,unified14:02
dhellmannlbragstad : it's what we've done elsewhere, although clarkb pointed out that not having overlap between ocata and pike for pbr may cause issues14:03
dhellmanntonyb : I'd like your input on whether we should change pike's pbr settings back to >=1.8 because of clarkb's comments14:03
dhellmanntonyb : see http://eavesdrop.openstack.org/irclogs/%23openstack-shade/%23openstack-shade.2017-03-14.log.html for the logs14:04
dhellmannprometheanfire : ^^14:04
lbragstaddhellmann ok - i'm just double checking before i start approving those changes for identity related projects14:05
prometheanfiredhellmann: ya, I remember him (or someone) pointing that out, but it hasn't caused problems for the upgrade gating that I know of14:07
*** ihrachys has joined #openstack-requirements14:08
dhellmannlbragstad : yeah, I can't give you a clear yes or no. clarkb raised some concerns, but not in this channel or with the requirements team, so we need to get them to think about it.14:08
prometheanfirethough if we can do it it'd just be preventitive care14:08
prometheanfirewhich is good14:08
dhellmannprometheanfire : apparently it caused some issues for shade somewhere, but I don't have the full details14:08
prometheanfireah14:08
prometheanfirehaving overlap would make packaging a little easier14:08
dhellmannif we do it, I think the flag for sphinx to treat warnings as errors will always be false, but that's what it was before14:09
dhellmannso I think it's probably safe to lower the min version14:10
dhellmannI haven't given it a lot of thought though14:10
prometheanfirewhere does sphinx enter into this?14:11
prometheanfirelbragstad: as far as the diff goes, the only thing that may change is pbr14:13
lbragstadprometheanfire yeah - that's what i was thinking14:14
lbragstadprometheanfire everything looks ok in IMO14:14
*** amoralej|lunch is now known as amoralej15:02
*** karthikpr has joined #openstack-requirements15:10
*** karthikpr has quit IRC15:13
*** armax has joined #openstack-requirements15:37
*** karthikpr has joined #openstack-requirements16:07
*** karthikpr has quit IRC16:08
*** udesale has quit IRC16:12
*** robputt_ has quit IRC16:28
openstackgerritSaad Zaher proposed openstack/requirements master: update constraint for python-freezerclient to new release 1.3.0  https://review.openstack.org/44590516:30
*** robputt has joined #openstack-requirements16:30
*** karthikpr has joined #openstack-requirements16:34
*** strigazi is now known as strigazi_AFK16:39
openstackgerritSean McGinnis proposed openstack/requirements master: Raise python-cinderclient to 2.0.1  https://review.openstack.org/44606416:53
openstackgerritOpenStack Proposal Bot proposed openstack/requirements master: update constraint for python-cinderclient to new release 2.0.1  https://review.openstack.org/44606616:55
*** karthikpr has quit IRC17:12
*** rtheis has joined #openstack-requirements17:13
*** rtheis has quit IRC17:16
amoralejdhellmann, question about https://review.openstack.org/#/c/442913/ apparently is adding a pike release into stable/ocata u-c, is that correct?17:24
*** karthikpr has joined #openstack-requirements17:30
*** jpich has quit IRC17:31
*** karthikpr has quit IRC17:32
dhellmannamoralej : it looks like that is in fact a pike release. tonyb ^^17:37
dhellmannprometheanfire : ^^17:37
*** karthikpr has joined #openstack-requirements17:37
dhellmanndirk : ^^17:37
prometheanfirelooking17:37
prometheanfire1.0.1?17:38
prometheanfireand commit message makes me think it's targeted to ocata17:38
prometheanfireanyway, need to get food while I can17:38
dhellmannit looks like I should have been more careful with that 1.0.1 release tag17:40
amoralejdhellmann, tagging 1.0.1 in master is effectively blocking new releases in stable/ocata, or am i missing something?17:41
dhellmannamoralej : yes, I messed up. we can do a 1.0.2 from stable/ocata after the fixes are backported17:42
amoralejalso, commit message in https://review.openstack.org/#/c/442913/ is confusing as it seems 1.0.1 is required for messaging in pike, not ocata but they are adding it in u-c in stable/ocata because it's not properly updated in grenade jobs17:43
dhellmannthat part i dont understand17:43
amoralejwhat seems not to be the right fix17:43
amoralejdhellman, iiuc package is not being properly upgraded in grenade jobs when upgrading from ocata to master so they are forcing to install the required one in master since the beginning17:45
*** jd_ has joined #openstack-requirements17:45
jd_howdy17:45
dhellmannamoralej : I have no idea about any of that, I wasn't involved. I've asked gordc and jd__ to join us here. I'm going to work on improving validation in the releases repo, but they're going to have to work on fixing the rest of it.17:46
dhellmannhi, jd_17:46
dhellmannhttps://review.openstack.org/#/c/442913/ has introduced a pike series library into the ocata series tests17:46
dhellmannwe need to undo that17:46
amoralejthanks for your help dhellmann17:46
dhellmannand then get a release from the ocata branch instead17:46
dhellmannI should have noticed that 1.0.1 was on master, not ocata, and asked for a different version number there, which would have made the rest of this more obviously wrong17:47
jd_oh ok so the release was made in some bizzare way?17:48
jd_gordc might know better than me the root of this patch anyway17:49
dhellmannjd_ : the release was cut from master, yeah17:49
jd_dhellmann: what can I do to help?17:49
jd_push a button?17:49
dhellmannwe need you to backport whatever fix went into 1.0.1 onto stable/ocata, then we can release 1.0.2 from stable/ocata and we can update the constraints to use that17:49
dhellmannthat way packagers watching that branch will actually get the released version17:50
prometheanfireyep17:50
* jd_ digs into that17:51
amoralejjd_ according to message in https://review.openstack.org/#/c/442913/ 1.0.1 is not really required for ocata but for pike, u-c bump in stable/ocata was only to workaround issue in grenade jobs not updating it properly17:53
amoralejthat's my understanding17:53
jd_so IIUC it's https://review.openstack.org/#/c/446090/ that is required for Ocata too because the oslo.messaging stuff is too recent otherwise17:54
jd_and that's why gordc released 1.0.117:54
jd_and made it happen on Ocata17:54
*** armax has quit IRC17:55
jd_amoralej: though what's the problem with 1.0.1 in the end being pulled? any error?17:56
*** karthikpr has quit IRC17:56
amoralejjd_ using library from master branch in stable/ocata builds, that's the problem17:57
*** gordc has joined #openstack-requirements18:12
gordcdhellmann: sorry, just came back from lunch. did you need more details on my patch?18:13
dhellmanngordc : check the scrollback for this channel. we need a new 1.0.2 on stable/ocata to avoid having packagers put 1.0.1 from pike into the ocata series18:13
gordcbasically relates to this: http://lists.openstack.org/pipermail/openstack-dev/2017-March/113506.html18:13
gordcyeah, i just read it.18:14
gordcor up to whatever is in eavesdrop18:14
dhellmannthere may be a better fix to the original problem, but from the release team's perspective we need to deal with the release, too18:14
gordci see. didn't realise libs couldn't cross branches18:14
dhellmannyeah, it causes issues downstream so we try to avoid it18:15
dhellmannI missed that when I was reviewing the release request, so I've added some extra validation to the releases repo18:15
gordcwell the release was suppose to be for master/pike... it just happens that it causes issue with our grenade because ocata pseudo-cap doesn't play well with pike18:16
dhellmannok, then I should have asked you to make the version 1.1.0 to save space for patch releases on the stable branch18:17
gordci see. i'll keep that in mind next time as well. wasn't' aware libs couldnt' exists across branches downstream18:18
dhellmannit sounds like the proper fix will need to be a change somewhere in devstack, unless we can put the middleware in the constraints list18:18
dhellmannyeah, it should work but it makes life a lot more complicated for packagers so we try to help them out by at least keeping our releases in the right series18:19
dhellmanngordc : so you're saying that because nothing upgrades ceilometermiddleware as a side-effect of upgrading a service, it's not upgraded at all?18:20
gordcdhellmann: i didn't check if it was possible with fix in devstack. what was happening was that when grenade updates services, it will update the requirements. but ceilometermiddleware isn't in anyone requirements. not sure how to hack that.18:20
dhellmanniirc, grenade just does a pip -U on the service, and the requirements come in for free. so it sounds like it needs to be smart enough to look for ceilometermiddleware somewhere in ther18:21
dhellmannthere18:21
gordcdhellmann: right. so in our grenade, pike would be testing against pike requirements, except ceiloemtermiddleware which remains stuck at ocata18:21
dhellmannright18:21
dhellmannok, I think you had 90% of the right fix.18:21
gordcceilometermiddleware isn't actually in an service's requirement, that's the issue i couldn't solve18:21
dhellmannif you backport whatever change was needed in ceilometermiddleware to your stable/ocata branch, we can tag 1.0.2 and we can make the constraints point to that18:22
dhellmannideally devstack or grenade would try to explicitly upgrade the middleware, since that's the tool responsible for installing it18:22
dhellmannbecause you're going to have the same problem the next time something in the middleware isn't compatible with the new series18:22
dhellmannbut that's probably a longer-term fix than just getting the release straightened out18:23
dhellmanngordc : make sense?18:23
gordcagreed. was banking on never touching ceilometermiddleware again ;)18:23
dhellmannheh18:23
dhellmannlet me know if I can help with stable reviews, and the new release18:23
gordci'll backport patch18:23
* gordc assuming jd_ didn't do it yet18:23
gordcnevermind he did.18:24
dhellmannoh, I think he did, so look first18:24
dhellmanngordc : I think https://review.openstack.org/#/c/446090/18:24
gordcdhellmann: i'll add a 1.0.2 release when it merges.18:25
dhellmanngordc : ++18:25
dhellmannamoralej : ^^18:25
amoralejgordc, dhellmann, thanks for fixing this!18:30
*** armax has joined #openstack-requirements18:30
jd_yeah I just did not press the button until you were back gordc to be sure, but cool thanks :)18:30
dirkdhellmann: thanks for the ping, will double check what happened in packaging18:42
*** karthikpr has joined #openstack-requirements19:13
*** karthikpr has quit IRC19:14
*** amoralej is now known as amoralej|off19:20
*** gordc has quit IRC19:48
*** stream10 has joined #openstack-requirements20:40
*** stream10 has quit IRC21:06
*** sdague has quit IRC21:09
*** ihrachys has quit IRC21:27
dasmo/21:47
dasmhey, i'm trying to force gate to install latest version of neutron-lib21:47
dasmhttps://review.openstack.org/#/c/416302/16/requirements.txt21:47
dasmbut it gives me hard time: http://logs.openstack.org/02/416302/16/check/gate-tempest-dsvm-neutron-full-ubuntu-xenial/edc4279/logs/devstacklog.txt.gz#_2017-03-15_20_41_15_33221:47
dasmneutron_lib is not installed at all21:47
dasmis there any check, or maybe -e is prohibited from requirements?21:48
dasmmaybe there is a better solution to install latest lib? I've read about LIB_FROM_GIT=neutron_lib but I'm not sure how to force dsvm-neutron-full job to get it21:49
dasm(probably there is a better solution :) )21:49
dasmbtw. purpose of testing latest neutron-lib is to ensure, that we won't break anything with new release of library21:51
*** armax has quit IRC22:19
*** ihrachys has joined #openstack-requirements22:56
*** ihrachys has quit IRC23:07
*** ihrachys has joined #openstack-requirements23:08
*** ihrachys has quit IRC23:10
*** ihrachys has joined #openstack-requirements23:12
*** IgorYozhikov has quit IRC23:17
*** IgorYozhikov has joined #openstack-requirements23:17
*** ihrachys has quit IRC23:17
*** ihrachys has joined #openstack-requirements23:39
*** ihrachys has joined #openstack-requirements23:39
*** ihrachys has quit IRC23:44

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