Wednesday, 2019-05-08

*** hongbin has joined #openstack-requirements01:31
*** eandersson has quit IRC03:13
*** udesale has joined #openstack-requirements03:55
*** hongbin has quit IRC04:19
openstackgerritMerged openstack/requirements master: Add missing format arg for missing g-r reqs  https://review.opendev.org/65703704:24
*** dims has quit IRC05:32
*** dims has joined #openstack-requirements05:33
*** udesale has quit IRC06:05
*** udesale has joined #openstack-requirements06:05
*** dims has quit IRC06:16
openstackgerritOpenStack Proposal Bot proposed openstack/requirements master: Updated from generate-constraints  https://review.opendev.org/65773806:27
*** dims has joined #openstack-requirements06:42
*** dims has quit IRC06:49
*** dims has joined #openstack-requirements06:54
*** udesale has quit IRC07:03
*** udesale has joined #openstack-requirements07:03
*** jpich has joined #openstack-requirements07:54
*** zbr|pto has quit IRC10:42
*** udesale has quit IRC11:14
*** jpich has quit IRC11:47
*** jpich has joined #openstack-requirements11:48
*** zbr has joined #openstack-requirements12:25
*** zbr has quit IRC12:26
*** samueldmq has joined #openstack-requirements13:09
*** davee__ has joined #openstack-requirements13:10
*** davee_ has quit IRC13:11
smcginnisSo what's the plan on the u-c redirects on master again? https://review.opendev.org/#/q/owner:tonybrad+status:open13:49
prometheanfiresmcginnis: the open task here https://storyboard.openstack.org/#!/story/171900613:51
prometheanfiresmcginnis: I don't know if we decided early or late switching, I think we all prefer early though13:51
smcginnisprometheanfire: Maybe we should suggest to that person that they get them all updated to the redirect URL since they are going through every repo.13:52
prometheanfirewell, tony is the right person, but he's asleep13:53
prometheanfireand that link is for tonybrad, which I don't think is the same person :P13:53
smcginnisNo, but hoping to head of the churn if they are going to be mucking in every repo and then we go back and change it again in a few days.13:54
smcginnisI guess we can leave it to tonyb[m]13:54
prometheanfireah, ya13:55
*** dangtrinhnt has quit IRC14:17
tonybsmcginnis: The plan is to ask the community.  We have 2 main options14:32
tonyb1) master always points to master and we switch to the series name after branching ; or14:33
tonyb2) at branch time we switch to the next series name on master14:33
smcginnisDon't we want both of those?14:34
smcginnisI guess the question is on the implemntation of 1. Do we want it to point to opendev.org/openstack/requirements master or the redirect URL to master.14:34
tonyboption 2 have benefits as we could land a semver: feature in the commit message to help packagers, but you said we were already doign that with the rno chnage so it's less apprealing14:34
smcginnisIf it's the first, then the patches that person has up are good and we can approve them.14:34
smcginnisWe do the semver: feature with the other stable branching. I definitely thing we should update that to use the new redirect URL for the stable branch too.14:35
tonybtonybrad's patches are wrong as they're not using the static urls we created ... well at least the first one isn't I didn't check the others14:37
tonybI'll make time to start the discussion on the mailing list14:38
smcginnistonyb: OK, that was my main question. If the URLs he is using are not what we want, we should head those off and get him to use the status URLs.14:39
smcginnis*static14:39
smcginnisRather than letting those go through, then come back a short while later just to update them again.14:39
tonybsmcginnis: Yup.  I'll -1 them with a comment that "please wait, we'll get there"14:41
smcginnis++14:41
prometheanfiretonyb: thanks14:44
tonybprometheanfire: np14:45
tonybprometheanfire: for the recrd I'm in MA for the next couple of days14:45
prometheanfiretonyb: I forgot you are US time this week14:45
prometheanfireya14:45
* prometheanfire goes back to evaluating health insurance14:45
*** ccamacho has joined #openstack-requirements15:10
tonybprometheanfire: work has been pretty 'high focus' so I haven't been able to really do the community stuff that'd benefir from being in this TZ15:11
*** altlogbot_2 has quit IRC15:21
tonybokay those have been reviewed, only one merged before we go to it so not too terrible15:21
*** irclogbot_2 has quit IRC15:22
*** altlogbot_3 has joined #openstack-requirements15:22
*** irclogbot_0 has joined #openstack-requirements15:24
*** altlogbot_3 has quit IRC15:27
*** altlogbot_1 has joined #openstack-requirements15:28
*** irclogbot_0 has quit IRC15:28
*** irclogbot_0 has joined #openstack-requirements15:30
prometheanfirejungleboyj: thanks for the email15:33
jungleboyjprometheanfire:  ?15:35
prometheanfirefor the cinder reqs one15:35
jungleboyjprometheanfire:  Welcome.  Sadly, don15:36
jungleboyj't remember doing that but I believe you.  :-)15:36
jungleboyjAre you talking about Python3 ?15:37
prometheanfireya15:37
jungleboyjAh, you are welcome.  :-)15:37
prometheanfiretonyb dirk smcginnis: if you have time... https://review.opendev.org/65739515:40
prometheanfiregonna bring that up at meeting time15:40
smcginnisYeah, that's an annoying one.15:41
smcginnisShould we have him break it out into different patches so the ones that actually look OK can get through?15:41
smcginnisSome would be better than none.15:41
prometheanfireya, there's an email on the list about cinder requirements py3 stuff (called out in review)15:42
*** e0ne has joined #openstack-requirements15:50
*** e0ne has quit IRC15:53
tonybprometheanfire: when is meeting time?15:54
* tonyb can't clock right now15:54
tonybdirk: I've commented on the oslo.rootwarp changes15:55
tonybdirk: +1 to master, still a (now largley procedural) -1 on stable/*15:56
prometheanfiretonyb: 1530 central15:56
prometheanfireso 1630 for you, we could have it earlier since we are all in the US now15:56
tonybprometheanfire: except dirk15:57
prometheanfiretonyb: earlier is better for him15:57
prometheanfirelater better for you :P15:57
tonybLet's just leave it where it is16:00
tonybI'm just -1'ing a meeting invite that clashes16:00
tonybI'd like to avoid to many moving parts16:00
prometheanfirek16:03
*** e0ne has joined #openstack-requirements16:11
*** e0ne has quit IRC16:26
*** e0ne has joined #openstack-requirements17:10
*** e0ne has quit IRC17:12
*** e0ne has joined #openstack-requirements17:18
*** e0ne has quit IRC17:21
*** jpich has quit IRC17:35
*** e0ne has joined #openstack-requirements17:59
*** e0ne has quit IRC18:07
dirktonyb: you moved to the US?18:30
tonybdirk: not yet, Just working from here for this week19:08
prometheanfireplanned?19:09
tonybprometheanfire: It's an open option at the moment19:09
tonybprometheanfire: it's a big and expensive thing to move a family across the globe19:10
prometheanfireyep19:11
dirkYeah19:18
dirkDo we have a patch for the keyring problem?19:22
dirkLooks like it became py3 only19:22
dirkNot exactly sure how we managed to get into that situation19:22
prometheanfirelook at tornado, not sure that helps though19:25
smcginnisSeeing this happen more and more. Anyone know what's going on there? http://logs.openstack.org/34/647934/3/check/openstack-tox-py27/93180f1/job-output.txt.gz#_2019-05-08_16_59_54_54426519:39
smcginnisWe have caps in place for py2, but it still tries to pull in the py3 version.19:40
prometheanfiresmcginnis: I think it's a bug, tornado does the same thing iirc19:41
* smcginnis will be very happy when we can drop py219:42
prometheanfireyep19:43
tonybI can't explain *how* but it's like taskflow isn't getting installed in phase 119:55
tonybThat's a really puzzling issue19:56
tonybsmcginnis: is it just a tox -epy27 from current cinder master?19:56
smcginnistonyb: Yeah, I've only seen it on py27.19:57
smcginnisEarlier in the log, it shows it gets the latest taskflow version that has the py version caps, but then later appears to pull in the wrong dependencies.19:57
smcginnisGuessing stable versions of taskflow will need to add those caps, as they just added it recently and it's only in the latest release.19:58
smcginnisCinder should probably raise the lower constraint for taskflow to make sure the newest one is used too.19:58
smcginnisMaybe I'll try that and see if it makes any difference.19:58
tonybI'll go through that log carefully we're clearly missing something20:00
prometheanfiremeeting in 3020:00
tonybOhhh the cinder toxenv looks wrong20:01
tonybYeah it's cinder bug20:02
tonybfunny it's taken that long to uncover20:02
smcginnisReally? What's wrong with it?20:03
tonybsmcginnis: you shall have to wait grasshopper while I wite the commit message ;P20:06
smcginnis:)20:06
tonybsmcginnis: https://review.opendev.org/65788120:12
*** ccamacho has quit IRC20:13
*** prometheanfire has quit IRC20:14
smcginnisThanks!20:15
*** evrardjp has quit IRC20:15
*** evrardjp has joined #openstack-requirements20:16
*** prometheanfire has joined #openstack-requirements20:16
smcginnisReally odd that that was never caught before.20:17
tonybThat is indeed odd20:24
tonybI wonder if the move to opendev hasn't somehow altered the content of the mirrors?20:24
prometheanfire5 min20:24
tonybsmcginnis: how long as it been blocked?  just today?20:24
tonybsmcginnis: py27 passed zuul20:26
smcginnistonyb: Yeah, just started noticing some failures today. And it's not every time, but seemed like it was increasing in frequency.20:27
prometheanfiremirror?20:27
openstackgerritDirk Mueller proposed openstack/requirements stable/stein: Add safety check output to the linters output  https://review.opendev.org/65708020:28
tonybprometheanfire: bandersnacth or whatever it's called20:28
openstackgerritDirk Mueller proposed openstack/requirements stable/rocky: Add safety check output to the linters output  https://review.opendev.org/65710620:28
tonybsmcginnis: Well that's very strange I wonder if it's worth seeing if it's failing on a specific provider20:28
smcginnisI think they switched from bandersnatch to a reverse proxy cache thing.20:28
prometheanfire#startmeeting requirements20:30
openstackMeeting started Wed May  8 20:30:04 2019 UTC and is due to finish in 60 minutes.  The chair is prometheanfire. Information about MeetBot at http://wiki.debian.org/MeetBot.20:30
smcginnisIt is odd to me the log showed it picked up taskflow 3.4.0 earlier though. That version should have pulled in the right dependencies.20:30
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:30
*** openstack changes topic to " (Meeting topic: requirements)"20:30
openstackThe meeting name has been set to 'requirements'20:30
prometheanfire#topic roll call20:30
*** openstack changes topic to "roll call (Meeting topic: requirements)"20:30
smcginniso/20:30
prometheanfiretonyb, prometheanfire, number80, dirk, coolsvap, toabctl, smcginnis, dhellmann ping20:30
prometheanfireo/20:30
dirko/20:31
prometheanfire#topic Any controversies in the Queue?20:32
*** openstack changes topic to "Any controversies in the Queue? (Meeting topic: requirements)"20:32
tonyb\o20:33
smcginnisThe Cinder driver one.20:33
prometheanfirerequests20:33
prometheanfireand safety check in linters20:33
prometheanfirebut that's it20:33
prometheanfireso, first, requests20:33
prometheanfiredirk: want to take that?20:33
prometheanfireor talk about it20:33
* tonyb[m] lost connectivity to his normal IRC account20:34
prometheanfiretonyb: k20:34
dirkprometheanfire: no updates yet, I started runnign the local tests today but then meeting madness started (not this meeting)20:35
prometheanfireof course, this meeting is insanity20:35
tonyb[m]insanely good!20:35
prometheanfiredirk: ok, please update with your results, you want to update to the new (unpublished) release as well?20:36
prometheanfiredirk: update the list that is20:36
dirkprometheanfire: yep20:36
prometheanfirecinder driver review, I think we are good here, dirk and tonyb asked them to split the review20:37
dirkI"m also trying to comment on funghi's topic20:37
tonyb[m]I do think that some of the 'problematic' ones will need more work so it might also be good to make the same split on the cinder side20:38
dirkit looks like both kolla and loci seem to be using "our" constraints20:38
prometheanfiredirk: ya, it is a point that's been brought up before20:38
prometheanfiretonyb: yep, they emailed the list statting they may have to do that20:38
prometheanfiredirk: osa uses them but can add exceptions20:38
tonyb[m]fungi's topic?20:38
dirkfungi left a comment questioning that we change uc on stable branches for security sake20:39
prometheanfiredon't update constraints becaues then people will expect it20:39
dirkhe is afraid that it is a road to regressions20:39
prometheanfireit in the list for the requests update thread20:39
fungiyep20:40
fungithat's a reasonable summary20:40
prometheanfireok, safety check in linters20:41
tonyb[m]Oh right I follow nwow20:41
tonyb[m]now even20:41
prometheanfirefor this one I know it runs fast but I don't like conflating lint checks and safety type checks in one 'yes/no'20:42
prometheanfireright meow?20:42
tonyb[m]I think that's fine20:42
dirkprometheanfire: its the same like other projects they run pep8/flake8 and bandit in the same job20:42
fungiif you need to update requests to a new release to avoid a security flaw in it, you may in turn need to update to a newer urllib3 and that may in turn require newer... on down until you hit something which needs updating in one of our projects to support20:43
dirkprometheanfire: technically the tox -epep8 should be renamed to tox -elinters imho20:43
prometheanfirethat's true, and goodenough for me, if we need to split later on we can20:43
tonyb[m]I know just beacuse others do it isn't a good reason, but plenty of other places do linting a checking at the same time20:43
prometheanfiredirk: that's true too20:43
prometheanfirefungi: yep20:43
dirkprometheanfire: therewas a plan to rename pep8 to linters but it seems with zuulv3 this is now super painful *as you have to land a change in 1 billion repos20:43
prometheanfirelol20:43
fungior super easy to just change in your repo and ignore everyone else? ;)20:44
prometheanfireok, any other controversies?20:44
dirkfungi: I agree, requests is annoying (also that it is branchless and doesn't maintain older versions with security fixes)20:44
fungii doubt it's the only one of our ~600 constraints entries which has those characteristics20:44
tonyb[m]fungi: true20:44
dirkfungi: I ran the saftey security checker against stable/pike the list is not short but its just a few packages20:45
dirkfungi: all the *good ones* of course (pycrytpo, cryptography, django, requests, ...)20:45
fungialso by the time security "fixes" percolate through our backporting of constraints bumps, deployers will have already needed to solve this on their side (or else they don't actually care about the security of their deployments, really)20:45
prometheanfirefungi: it's the latter20:46
fungiif you're using a deployment based on distro packages of dependencies, your distro has probably already pushed out fixed packages before we even know there's a vulnerability20:46
prometheanfire#topic open floor20:46
*** openstack changes topic to "open floor (Meeting topic: requirements)"20:46
prometheanfireya, if using disto packages20:46
dirkfungi: all the container deployers that opensetack offers (kolla, loci, osa) seem to just use upperconstraints20:47
dirkfungi: building binary wheels from that20:47
fungithat's frightening20:47
dirkfungi:  it is20:47
dirkto talk about something more fun20:47
dirkgiven that there are a thousand "switch to opendev.org url" reviews out there, we need to accellerate our efforts to push out *sane* upper-constraint urls20:48
tonyb[m]Sure20:48
dirkI have seen two to three variants, depending on who did the review. also some reviews that point to 404 urls (whcih pip in -c seems to happily ignore and just install unconstrained)20:48
dirkso I think I pushed a review to add TOX_CONSTRAINTS20:49
prometheanfiredirk: they do, but if the security check was gated on in them they could do that20:49
dirkbut I can't find it anymore20:49
tonyb[m]:(20:49
tonyb[m]I think we shoudl just do it and ask for forgiveness for not doing everything in one hit20:50
dirkprometheanfire: right, but isn't it better to maintain that list in one place than having 3 different deployers compete in the combination of broken dependency versions they choose20:50
dirkwhat we could do is separate it out into unsafe-but-working-constraints.txt and safe-but-potentially-broken-constraints.txt20:50
tonyb[m]I feel like it's basically a 5-line shell script maybe 10 if I handle errors20:50
dirkthen people can chose if they want stability or safety ;-]20:51
prometheanfiredirk: that's true, but also makes security 'our problem' rather than each deployment project's problem20:51
dirkprometheanfire: one thing I want to do is to switch to a pure-ascii output in the safety check20:51
dirkas it doesn't render too well from logs.o.org (it looked great when run locally)20:51
prometheanfireya20:52
dirkprometheanfire: our problem is to review, not to fix stuff20:52
prometheanfiretonyb: so you are accelerating the TOX_CONSTRAINTS thing?20:52
dirkand I can take the reviews20:52
tonyb[m]prometheanfire: I don't have the bandwith for that work right now20:52
prometheanfiredirk: true, but that's a bit reductionist :P20:52
tonyb[m]prometheanfire: I can to the 'switch to https://releases.o.o/...' work on at least master and probably stable/*20:53
tonyb[m]prometheanfire: I doubt I'll have time to fix all the bitrot but I can start the process20:53
prometheanfiretonyb[m]: that'd be a good start and head off a bunch of the reviews20:53
tonyb[m]Yup20:54
tonyb[m]at least a few bad ones have merged20:54
prometheanfireyep20:54
prometheanfireanyone else have topics?20:54
smcginnisnot me20:54
dirktonyb:  https://review.opendev.org/657886 would be the first step I think20:56
prometheanfire#endmeeting20:56
*** openstack changes topic to "OpenStack Requirements - IRC meetngs on Wednesdays @ 07:00 UTC in here in #openstack-requirements - See agenda @ http://tinyurl.com/h44ryuw - IRC channel is *LOGGED* @ http://tinyurl.com/j38rk24"20:56
openstackMeeting ended Wed May  8 20:56:05 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:56
openstackMinutes:        http://eavesdrop.openstack.org/meetings/requirements/2019/requirements.2019-05-08-20.30.html20:56
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/requirements/2019/requirements.2019-05-08-20.30.txt20:56
openstackLog:            http://eavesdrop.openstack.org/meetings/requirements/2019/requirements.2019-05-08-20.30.log.html20:56
openstackgerritDirk Mueller proposed openstack/requirements master: Add safety check output to the linters output  https://review.opendev.org/65710521:04
tonybdirk: Can you point me at the 'keyring' issue?21:08
dirktonyb: http://logs.openstack.org/67/657167/2/check/requirements-integration/9d52644/job-output.txt.gz#_2019-05-08_11_08_25_53590521:10
dirktonyb: it seems in other cases it fails on networkx21:10
dirkwhats going on?21:11
tonybwell with a 30second look it seems similar to the cinder fix for networkx21:11
tonybWell for keyring I think g-r is wrong21:14
dirkRight but there wasn't a release recently so that should be a problem since forever21:17
tonybdirk: Yeah clearly something *else* has also changed21:17
tonybdirk: I'm going to play wack-a-mole with keyring as we're in the wrong but it's worth stepping back and workign out what chnaged.21:18
openstackgerritTony Breeds proposed openstack/requirements master: Cap keyring on python2  https://review.opendev.org/65789021:24
dirktonyb: left a NIT21:29
tonybdirk: ok21:31
openstackgerritTony Breeds proposed openstack/requirements master: Cap keyring on python2  https://review.opendev.org/65789021:35
tonybdirk: fixed21:36
*** e0ne has joined #openstack-requirements23:35
*** e0ne has quit IRC23:52

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