| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-sdks - 2020-03-26 | |||
| 13:15:02 | openstackgerrit | Mark Chappell proposed openstack/ansible-collections-openstack master: New module: os_keystone_mapping_info https://review.opendev.org/713686 | |
| 13:15:03 | openstackgerrit | Mark Chappell proposed openstack/ansible-collections-openstack master: New Module: os_keystone_identity_provider https://review.opendev.org/714632 | |
| 13:15:04 | openstackgerrit | Mark Chappell proposed openstack/ansible-collections-openstack master: New Module: os_keystone_identity_provider_info https://review.opendev.org/714633 | |
| 13:15:05 | openstackgerrit | Mark Chappell proposed openstack/ansible-collections-openstack master: New Module: os_keystone_federation_protocol https://review.opendev.org/714991 | |
| 13:15:06 | openstackgerrit | Mark Chappell proposed openstack/ansible-collections-openstack master: New Module: os_keystone_federation_protocol_info https://review.opendev.org/714992 | |
| 13:28:37 | openstackgerrit | Monty Taylor proposed openstack/openstacksdk master: Add link to image sharing api docs https://review.opendev.org/677266 | |
| 13:47:18 | openstackgerrit | Monty Taylor proposed openstack/python-openstackclient master: Add libc6-dev to bindep https://review.opendev.org/715210 | |
| 13:50:14 | openstackgerrit | Monty Taylor proposed openstack/python-openstackclient master: Be explicit about python version in image https://review.opendev.org/715211 | |
| 13:50:50 | mordred | amoralej|lunch: ^^ the libc6-dev patch should fix the https://review.opendev.org/#/c/697444/ patch | |
| 13:51:06 | mordred | gah | |
| 13:51:13 | mordred | amotoki: ^^ | |
| 13:51:24 | mordred | amoralej|lunch: sorry - bad tab-complete | |
| 13:51:41 | openstackgerrit | Monty Taylor proposed openstack/python-openstackclient master: Adding options to user cli https://review.opendev.org/697444 | |
| 14:28:51 | gtema | nodepool builds seem to be failing everywhere in SDK | |
| 14:29:01 | gtema | I mean nodepool jobs | |
| 14:30:17 | mordred | there's an issue in setuptools | |
| 14:30:22 | mordred | that has been fixed | |
| 14:30:25 | gtema | ah, ok | |
| 14:30:42 | mordred | but it's gonna be a minute before it winds its way through the layers of things to dib | |
| 14:30:56 | gtema | oki, keep waiting ;) | |
| 14:30:59 | mordred | (the bug caused non-entrypoint scripts to lose their executable bit when they were installed) | |
| 14:31:12 | gtema | cool | |
| 14:31:17 | mordred | yeah. so awesome | |
| 14:31:51 | smcginnis | Hah, oops. | |
| 14:31:53 | gtema | but from our logs you don't see this really - just that it failed | |
| 14:55:38 | mordred | gtema_: have a sec for 2 easy patches: https://review.opendev.org/#/c/715210/ https://review.opendev.org/#/c/715211/ ? | |
| 14:58:00 | gtema | yupp, looking now | |
| 14:59:30 | mordred | gtema: thanks! | |
| 14:59:45 | gtema | should I +A for the py3.7? | |
| 15:00:03 | mordred | gtema: sure. it's a pretty mechanical change | |
| 15:00:13 | gtema | done | |
| 15:00:18 | mordred | I think "let's upgrade to 3.8" would be one where we shoudl actually discuss :) | |
| 15:00:29 | gtema | agree | |
| 15:01:12 | gtema | btw this libc - today figured out, that in my zuul F30 image does not include by default bzip2 - pretty weird | |
| 15:01:34 | mordred | gtema: yeah - I think we just had a patch for that in zuul | |
| 15:02:11 | mordred | oh even weirder ... | |
| 15:02:12 | gtema | can you please point me to it? I just did a dirty hack to keep it running | |
| 15:02:16 | mordred | https://review.opendev.org/#/c/715041/ | |
| 15:02:25 | mordred | but the issue was that it was only installing for rpm | |
| 15:02:32 | mordred | but I'd expect it to be installed on F30 | |
| 15:02:54 | mordred | oh - wait ... | |
| 15:03:02 | gtema | yeah, should have been there | |
| 15:03:15 | mordred | your zuul F30 image - you mean an F30 image you're using with zuul - not that you're running zuul in | |
| 15:03:34 | gtema | right - F30 image with jobs | |
| 15:04:04 | mordred | yeah - so - in opendev we try to install as little as possible in the images so that projects can express their depends in their bindep files | |
| 15:04:34 | mordred | so if you have a job fail due to lack of bzip2, you might need to add it to the bindep of the project in question? | |
| 15:04:41 | gtema | I remember it was working always fine, but today finally reenabled building docs and that is where I noticed it | |
| 15:04:47 | gtema | exact | |
| 15:05:00 | mordred | yeah - tox-docs is the thing that people were discussing yesterday | |
| 15:05:00 | gtema | https://opendev.org/zuul/zuul-jobs/src/branch/master/roles/fetch-sphinx-tarball/tasks/html.yaml | |
| 15:05:09 | mordred | there's a giant scrollback in the #zuul channel log about it | |
| 15:05:19 | mordred | I didn't follow the whole thing | |
| 15:05:24 | gtema | oh god, no interest for scroll | |
| 15:06:41 | mordred | gtema: https://review.opendev.org/#/c/715028 is what mnaser put together - I believe the idea is that gzip is more common | |
| 15:07:25 | gtema | yeah, this seem reasonable. I use zuul-jobs, so whenever it lands I get it as well | |
| 15:07:28 | mordred | however - if you had the bzip issue with tox-docs - it's likely that your zuul executor did not have bzip - and if you're running a zuul from the container images - they were missing bzip2 because of that bindep line. it's all a bit confusing | |
| 15:08:02 | vphilippon | Hello! I think I've stumbled on an issue with Python openstacksdk 0.44.0 dependencies. In short, it depends on futurist>=2.1.0, which is Py3-only, effectively making openstacksdk also Py3-only. | |
| 15:08:14 | gtema | exact - running zuul itself in containers | |
| 15:08:33 | mnaser | seems like everyone is hitting that heh | |
| 15:08:39 | gtema | underneath podman as non-root - so even more cool bels and whistles | |
| 15:14:22 | vphilippon | I barged in with that message, sorry. Is there a channel better suited for Python openstacksdk specific issues? | |
| 15:15:01 | mordred | vphilippon: yes - starting with this openstack release openstacksdk is python3 only | |
| 15:15:16 | mordred | vphilippon: let me find the version you should pin to if you're using py2 | |
| 15:16:12 | vphilippon | @mordred: Thanks. Although, the missing Requires-Python metadata will make a poor user experience with pip then :( | |
| 15:16:58 | mordred | vphilippon: agree - I'll get that fixed | |
| 15:17:11 | vphilippon | The only solution I know for this would be to pull v0.44.0 from pypi and republish it with the metadata | |
| 15:17:13 | mordred | vphilippon: 0.40.0 is the first release in which python2 is no longer tested/supported | |
| 15:17:38 | mordred | we can't do that - republishing a release breaks the universe. we can publish a fixed 0.45 though | |
| 15:18:00 | vphilippon | Because of 0.44.1 is released, pip will go back to 0.44.0, that is purely broken | |
| 15:18:15 | vphilippon | Because if* | |
| 15:19:18 | openstackgerrit | Monty Taylor proposed openstack/openstacksdk master: Add requires-python entry indicating 3.6 is required https://review.opendev.org/715243 | |
| 15:19:32 | mordred | vphilippon: yeah - I think we can remove 0.44 once 0.44.1 is there | |
| 15:20:00 | vphilippon | Oh, that works too! | |
| 15:20:41 | vphilippon | Even better, taking note of that option (this not the first time I get to report this to maintainers, sadly) | |
| 15:20:51 | mordred | smcginnis, gtema: ^^ see discussion and patch - let's land that and cut an 0.44.1 real quick | |
| 15:21:00 | mordred | actually - let me add a release note explanation real quick | |
| 15:21:12 | gtema | sure, but we can't unless nodepool build are fixed ;) | |
| 15:21:37 | gtema | perhaps also removing "Programming Language :: Python :: 2" | |
| 15:22:57 | openstackgerrit | Monty Taylor proposed openstack/openstacksdk master: Add requires-python entry indicating 3.6 is required https://review.opendev.org/715243 | |
| 15:23:03 | vphilippon | Thanks for the quick response btw :) | |
| 15:23:03 | smcginnis | mordred: Good on the new release. Not so sure about removing anything. That's generally bad. And not clear what the issue is here. | |
| 15:23:03 | mordred | ++ | |
| 15:23:32 | openstackgerrit | Monty Taylor proposed openstack/openstacksdk master: Add requires-python entry indicating 3.6 is required https://review.opendev.org/715243 | |
| 15:23:58 | gtema | yupp | |
| 15:24:01 | mordred | smcginnis: so - the situation is that we neglected adding requires-python>=3.6 to the first release where that was actually physically true | |
| 15:24:18 | mordred | which means python2 installs of openstack with no versions are finding it and trying to install it | |
| 15:24:28 | smcginnis | I'd say only about 50% (or less) of our ussuri deliverables have done that. | |
| 15:24:51 | mordred | yeah- but openstacksdk is a much wider audience of people who pip install it | |
| 15:24:57 | mordred | since it's end-user and not operator | |
| 15:25:00 | smcginnis | I guess openstacksdk is probably more prevalent outside of openstack, so we can't rely on upper-constraints. | |
| 15:25:02 | mordred | yeah | |
| 15:25:03 | smcginnis | Yeah | |
| 15:25:05 | smcginnis | ;) | |
| 15:26:05 | mordred | so - in this case, I think releasing a quick 0.44.1 bugfix and then removing 0.44.0 from pypi will unbreak people - as long as we wait for u-c to bump to 0.44.1 in openstack before doing so | |
| 15:26:14 | mordred | obviously a discussion for release team | |
| 15:26:30 | mordred | and first step is getting the fix landed so we can release 0.44.1 which is uncontroversial | |
| 15:26:53 | mordred | gtema: I think maybe let's disable the nodepool test for the requires-python fix so we can get it landed, then re-enable | |
| 15:27:07 | gtema | ok, agree | |
| 15:27:25 | gtema | but then also have otc vendor profile fix in | |
| 15:28:25 | mordred | ++ | |