| *** brinzhang has joined #openstack-requirements | 00:01 | |
| *** brinzhang_ has joined #openstack-requirements | 01:00 | |
| *** brinzhang has quit IRC | 01:04 | |
| *** CrayZee has joined #openstack-requirements | 01:10 | |
| *** shachar has quit IRC | 01:13 | |
| *** brinzhang has joined #openstack-requirements | 01:25 | |
| *** brinzhang_ has quit IRC | 01:29 | |
| *** brinzhang_ has joined #openstack-requirements | 01:54 | |
| *** brinzhang has quit IRC | 01:58 | |
| *** gouthamr has quit IRC | 04:15 | |
| *** gouthamr has joined #openstack-requirements | 04:16 | |
| openstackgerrit | OpenStack Proposal Bot proposed openstack/requirements master: Updated from generate-constraints https://review.opendev.org/681382 | 06:12 |
|---|---|---|
| *** spsurya has joined #openstack-requirements | 06:33 | |
| *** udesale has joined #openstack-requirements | 06:46 | |
| *** brinzhang has joined #openstack-requirements | 06:50 | |
| *** brinzhang_ has quit IRC | 06:53 | |
| *** brinzhang_ has joined #openstack-requirements | 07:10 | |
| *** brinzhang has quit IRC | 07:13 | |
| *** tosky has joined #openstack-requirements | 07:18 | |
| *** e0ne has joined #openstack-requirements | 07:22 | |
| *** e0ne has quit IRC | 07:22 | |
| *** brinzhang has joined #openstack-requirements | 07:51 | |
| *** brinzhang_ has quit IRC | 07:55 | |
| *** brinzhang has quit IRC | 08:09 | |
| *** zbr is now known as zbr|ruck | 08:23 | |
| *** e0ne has joined #openstack-requirements | 08:59 | |
| *** ccamacho has joined #openstack-requirements | 09:19 | |
| *** mugsie has quit IRC | 10:03 | |
| *** mugsie has joined #openstack-requirements | 10:05 | |
| *** prometheanfire has quit IRC | 10:22 | |
| *** prometheanfire has joined #openstack-requirements | 10:23 | |
| *** zbr|ruck is now known as zbr|lunch | 11:15 | |
| *** ccamacho has quit IRC | 11:45 | |
| *** spsurya has quit IRC | 12:10 | |
| *** udesale has quit IRC | 12:16 | |
| *** udesale has joined #openstack-requirements | 12:16 | |
| *** camelCaser has quit IRC | 12:53 | |
| *** camelCaser has joined #openstack-requirements | 12:55 | |
| *** udesale has quit IRC | 12:56 | |
| *** camelCaser has quit IRC | 12:59 | |
| openstackgerrit | OpenStack Proposal Bot proposed openstack/requirements stable/stein: update constraint for python-troveclient to new release 2.17.1 https://review.opendev.org/686611 | 13:10 |
| openstackgerrit | OpenStack Proposal Bot proposed openstack/requirements stable/queens: update constraint for oslo.messaging to new release 5.35.6 https://review.opendev.org/686615 | 13:13 |
| openstackgerrit | OpenStack Proposal Bot proposed openstack/requirements stable/rocky: update constraint for oslo.messaging to new release 8.1.4 https://review.opendev.org/686617 | 13:14 |
| *** zbr|lunch is now known as zbr|ruck | 13:25 | |
| *** camelCaser has joined #openstack-requirements | 13:43 | |
| *** gmann_afk is now known as gmann | 13:58 | |
| *** bnemec is now known as beekneemech | 14:54 | |
| *** efried has joined #openstack-requirements | 15:15 | |
| efried | prometheanfire: mordred and I have an interesting requirements dilemma, got a sec? | 15:16 |
| prometheanfire | efried: sure | 15:17 |
| efried | It looks like this: | 15:17 |
| efried | There's a fix in keystoneauth1 that, when applied, exposes a latent bug in openstacksdk. | 15:17 |
| efried | We have a fix in sdk which, as long as it's applied before/with the ksa fix, makes everything fine. | 15:17 |
| efried | But there's no requirement from ksa to sdk (which makes sense -- it's the other way around). | 15:17 |
| efried | So the question is: would adding the new rev of sdk to the lower-constraints of ksa do the trick, despite sdk not being in requirements.txt of ksa? | 15:18 |
| *** mordred has joined #openstack-requirements | 15:18 | |
| * mordred waves to efried | 15:18 | |
| efried | o/ I got started without you | 15:18 |
| mordred | ones | 15:18 |
| mordred | wait | 15:19 |
| mordred | o noes | 15:19 |
| efried | and it'll be another 10 minutes before eavesdrop catches up, so you'll just have to wonder. | 15:19 |
| * mordred is on the edge of his seat | 15:19 | |
| efried | prometheanfire: In case it matters, the changes in question are: | 15:20 |
| efried | ksa: https://review.opendev.org/#/c/685042/ | 15:20 |
| efried | sdk: https://review.opendev.org/#/c/685999/ | 15:20 |
| prometheanfire | ok, lower-constraints are used to have something to test against for lower bounds testing and to actually set a requirement in the requirements.txt file | 15:21 |
| prometheanfire | so if it's not in their requirements.txt it won't help much | 15:22 |
| mordred | efried: based on your comment on the change ... the only reason I'm saying that the ksa change depends on the sdk change is that landing and releasing the ksa change before the sdk change will break sdk | 15:22 |
| mordred | but - like - mostly just in the gate | 15:22 |
| prometheanfire | the best we can do is just fix it separately and have a release note stating that x-interaction was fixed in release y | 15:22 |
| efried | mordred: I thought if in the wild you applied the ksa fix without the sdk fix you would break your compute proxy | 15:22 |
| mordred | the ksa change doesn't ACTUALLY depend on the sdk change from a real-world pov | 15:22 |
| mordred | no - in the wild if you did that it should be fine - except for creating server groups with policies | 15:23 |
| efried | well yeah :) | 15:23 |
| mordred | so - ok - it would break in the wild :) | 15:24 |
| prometheanfire | not a good way to avoid that :( | 15:24 |
| efried | If that's the case, then probably the ksa reno should call that out and point to a bug | 15:24 |
| mordred | but - I think it should be _fairly_ safe if we just land and release the sdk fix before we land and release he ksa one | 15:24 |
| mordred | so you'd have to do some explicit work to break yourself | 15:24 |
| mordred | efried: good point | 15:24 |
| efried | yeah, for the most part it shouldn't happen, but it'd be nice to warn | 15:24 |
| mordred | I'll update the reno | 15:24 |
| efried | cool, thanks mordred & prometheanfire, I feel better :) | 15:25 |
| prometheanfire | :D | 15:26 |
| mordred | efried: how does https://review.opendev.org/#/c/685042/ look? | 15:30 |
| efried | mordred: It would be nice to link to *something* with more detail. Ideally a bug (story?) would be the thing, but if not, at least the change set(s). | 15:33 |
| efried | but otherwise, yeah, lgtm. | 15:33 |
| mordred | efried: you people with your actual bug/story tracking ability | 15:38 |
| efried | I know, I'm sorry, I'm SORRY! | 15:38 |
| mordred | efried: do you think https://review.opendev.org/#/c/685999/ has enough info to be useful to link to? | 15:38 |
| efried | mordred: yeah, I think that's good enough | 15:39 |
| efried | I'm just thinking from an operator's perspective they need to be able to understand what they need to do. | 15:39 |
| efried | and what will break if they don't | 15:39 |
| mordred | ++ | 15:39 |
| efried | conversely, when something breaks, something they'll be able to recognize when they go back and read the release notes (for the first time) | 15:40 |
| *** adriant has quit IRC | 15:59 | |
| *** tosky has quit IRC | 16:05 | |
| *** e0ne has quit IRC | 16:32 | |
| *** zbr|ruck has quit IRC | 16:39 | |
| *** zbr has joined #openstack-requirements | 16:51 | |
| *** efried has quit IRC | 17:56 | |
| *** zbr has quit IRC | 19:46 | |
| *** e0ne has joined #openstack-requirements | 19:50 | |
| openstackgerrit | Merged openstack/requirements stable/stein: update constraint for python-troveclient to new release 2.17.1 https://review.opendev.org/686611 | 19:57 |
| openstackgerrit | Merged openstack/requirements stable/queens: update constraint for oslo.messaging to new release 5.35.6 https://review.opendev.org/686615 | 19:57 |
| *** e0ne has quit IRC | 20:09 | |
| *** prometheanfire has quit IRC | 21:16 | |
| *** prometheanfire has joined #openstack-requirements | 21:17 | |
| *** tosky has joined #openstack-requirements | 21:31 | |
| *** tosky has quit IRC | 23:39 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!