Wednesday, 2022-06-15

opendevreviewOpenStack Proposal Bot proposed openstack/requirements master: Updated from generate-constraints  https://review.opendev.org/c/openstack/requirements/+/84587102:46
opendevreviewMatthew Thode proposed openstack/requirements master: Updated from generate-constraints  https://review.opendev.org/c/openstack/requirements/+/84587103:03
zigosean-k-mooney: I uploaded to Experimental especially to find the issues in 4.6.0 with the pseudo-excuse page, though Unstable still has 3.2.0.06:16
zigoThe thing is other software in Debian need >= 4.4.0, which is why a few DDs are pushing hard so I update jsonschema to something more recent.06:16
zigoWhich is why I'm asking if something can be done.06:16
zigo3.2.0 from nov 2019 is quite old ... :P06:17
rpittauhello everyone! We saw requirements dropped the u-c value for coverage for python3.6 recently, that broke our sushy-tools python3.6 tox job (we're keeping compatibility for the time being as it's branchless), any suggestion on how to work around that/fix it?08:04
sean-k-mooneyzigo: right but as i noted on the mailing list nova is not way its on 3.2.0 currently08:09
sean-k-mooneyzigo: its on 3.2.0 becaus of warlock which is used by glance cleint08:10
zigoRight.08:10
zigoThanks for this investigation.08:10
sean-k-mooneyzigo: warlock is the lib with the <4 cap so i wonder how hard it woudl be to drop that08:10
zigoHopefully, the fixed warlock can be released.08:10
zigoI wouldn't mind dropping warlock as you suggested...08:11
sean-k-mooneythey have not merged any patches in 2 years08:11
zigoOne less thing to maintain is always good.08:11
sean-k-mooneyim thinking the project is pretty dead08:11
sean-k-mooneyso ya i think we shoudl drop it if we can08:11
zigoIt used to be maintained by bcwaldon, though I'm not sure if he's still in the OpenStack game.08:12
zigo(he was a Glance maintainer)08:12
sean-k-mooneyya is galnce client still supported by the way08:15
sean-k-mooneyas in has everything been ported to osc08:15
zigoLooks like Brian is now working at: https://antaris.space/ so not OpenStack related anymore ...08:15
zigoI wouldn't mind if we dropped glanceclient ! :)08:16
sean-k-mooneynovaclint is partly deprecated by the way. its supported as a lib going forward but the cli part is frozen08:16
sean-k-mooneyeventually we want to drop it and have people use sdk but no timeline for that08:17
zigoHowever, if we can patch the issue out of glanceclient, that'd be better, so I could fix it in Debian Unstable (before Zed is released).08:17
sean-k-mooneyi know neutron is in a similar trasition not sure about glance08:17
sean-k-mooneyya so that woudl be my path forward08:18
sean-k-mooneypatch the issue out fo glance and drop warlock form global-requiremetns08:18
sean-k-mooneythen update json scep to say 4.4 if it does not rbeak anything then fix what is left to get 4.6 working in nova and then update uc to 4.608:19
fricklerzigo: sean-k-mooney: quite a can of worms we have there08:43
fricklerheat-translator 2.5.0 requires python-glanceclient, python-glanceclient 4.0.0 requires warlock, warlock 1.3.3 requires jsonschema<4,>=0.7, but you have jsonschema 4.6.0 which is incompatible.08:44
zigoAgreed. Though we can't stay stuck on a 3 years old version of jsonschema, at some point it needs to be fixed.08:44
fricklertalk to glance, I'd say. not sure what warlock actually does08:44
fricklerwe also have some other issues. like anyjson is no longer buildable. our whole CI only works because we are using a historically built wheel for it08:45
fricklerthings will fail miserably once we try to run u-c updates on python3.1008:45
sean-k-mooneyfrickler: i commented out anyjson to get to the warlock issue08:46
fricklerah, now I see that you found warlock already in the backlock08:46
fricklersean-k-mooney: I used our wheels cache instead, but yes08:47
fricklerpython-nss also seems unbuildable with openssl3 on Jammy08:47
sean-k-mooneyso what would it take to drop both fo those by the way08:47
sean-k-mooneywarlock looks simple to drop08:47
sean-k-mooneyis anyjson used much08:47
fricklernot so much I'd say, at least within openstack proper https://codesearch.openstack.org/?q=anyjson&i=nope&literal=nope&files=&excludeFiles=&repos=08:50
fricklernot sure how active murano-agent is these days08:50
fricklerrpittau: use yoga constraints for that job?08:51
rpittaufrickler: yep, that was taken into consideration, just maybe wondering if there was an alternative08:54
fricklerrpittau: the only alternative I see would be to stop using global-requirements for that project and set your own instead09:00
rpittaufrickler: thanks! I saw that done by swift for example, we'll discuss if it's worth keeping py3.6 support at this point09:01
*** tosky_ is now known as tosky09:42
sean-k-mooneywas it?11:01
sean-k-mooneythat seam like not a good thing in general11:02
sean-k-mooneye.g. if some project dont use global-requirements anymore11:02
sean-k-mooneydont we still requrire co installablity11:02
sean-k-mooneye.g. for it to be an offical project in the openstack namespace11:02
sean-k-mooneyfrom a governace perspecitve i tought the PTI with global requirements was a requirement11:03
sean-k-mooneyfrickler: so lookign at the second wip patch for jasonschema 4.6.0 vs my 4.0.1 a similar number of project are failing on both11:05
sean-k-mooneyso we proably shoudl go strait to 4.6.011:05
sean-k-mooneyand just have a one time pain11:05
sean-k-mooneyi was hoping we could advance the bump a few times in the 4 seriese11:05
sean-k-mooneyto reduce the scope of what we needed to fix11:06
sean-k-mooneywhich is why i started with 4.0.1 but if that fails and 4.6.0 fails there proably isnt much value in doing a seach to see if any of the intermedaries work11:06
fricklersean-k-mooney: ack, going to latest seems preferrable11:08
sean-k-mooneywe should be able to use a depend on form nova to the requriement patch to develop a patch to fix the compatiblity yes11:09
sean-k-mooneyand then flip that11:09
sean-k-mooneyonce it owrks11:09
sean-k-mooneywell or just do it locally i guess11:10
sean-k-mooneywe can manuyally install the newer version with pip11:10
sean-k-mooneyand then fix what is broken and just have the bump patch depend on it11:10
sean-k-mooneygmann: you mentioned another lib11:10
sean-k-mooneymove form v4 to v7 or something like that11:11
sean-k-mooneywere you working on a patch for that or planning to 11:11
*** tosky_ is now known as tosky11:55
opendevreviewOpenStack Proposal Bot proposed openstack/requirements master: update constraint for taskflow to new release 5.0.0  https://review.opendev.org/c/openstack/requirements/+/84598012:25
fricklersean-k-mooney: did you see this? openstack-placement 1.1.0 depends on jsonschema<3.0.0 and >=2.6.012:28
fricklerah, wait, that may be old versions due to pip trying to resolve other things12:29
fricklerhttps://zuul.opendev.org/t/openstack/build/49a23a47b6cd460daf4a334917fec7c012:29
sean-k-mooneyi didnt see that no but ill check placment12:31
sean-k-mooneyhttps://github.com/openstack/placement/blob/master/requirements.txt#L14=12:32
sean-k-mooneyjsonschema>=3.2.0 # MIT12:32
sean-k-mooneyso we shoudl be fine assuming its compatible12:32
fricklersean-k-mooney: yes, I think pip output is misleading. iiuc the real conflict is with warlock/python-glanceclient, which nova also depends on12:37
fricklerjust designate looks like it will need a proper fix, too https://zuul.opendev.org/t/openstack/build/75b6d1dff31e4af8b239f7b2e3086bbc12:37
sean-k-mooneywe should really move to sdk :)12:53
*** tosky__ is now known as tosky13:17
*** tosky is now known as Guest216913:29
*** tosky__ is now known as tosky13:29
*** tosky__ is now known as tosky13:58
johnsomfrickler Have you started a patch for designate or is it something I should work on?14:33
fricklerjohnsom: I didn't start yet, feel free to have a look14:39
johnsomfrickler Ack, I will look into it.14:39
johnsomThanks14:39
prometheanfirejust syncing now, looks like talk about removing caps only?15:18
fricklerprometheanfire: for jsonschema, the cap is implicit via a glanceclient dep, no direct action needed on the requirements side15:42
fricklerprometheanfire: for anyjson, it needs to be dropped completely IMO. the latest version is from 201215:43
fricklerit's one the the things listed in https://review.opendev.org/c/openstack/requirements/+/813302/3/upper-constraints.txt15:44
fricklergotta refresh those test jobs and maybe try to run propose-updates on py3.10, too15:45
fricklerthat'll certainly bring out more cruft15:45
prometheanfirefair on the anyjson15:47
prometheanfireif we can get 3.10 that'd be nice, but atm we can't run all the pythons in one place, which limits us15:47
prometheanfireopenstack/murano-agent is the only thing that really uses anyjson, I think15:48
johnsomFYI, I have posted the designate fix for jsonschema > 4 support: https://review.opendev.org/c/openstack/designate/+/84601415:49
opendevreviewDr. Jens Harbott proposed openstack/requirements master: WIP: Run a job without the pre-built wheels  https://review.opendev.org/c/openstack/requirements/+/81329216:09
opendevreviewDr. Jens Harbott proposed openstack/requirements master: DNM: Show failed builds and dependents  https://review.opendev.org/c/openstack/requirements/+/81330216:17
opendevreviewMerged openstack/requirements master: update constraint for taskflow to new release 5.0.0  https://review.opendev.org/c/openstack/requirements/+/84598016:20
gmannsean-k-mooney: that is on jsonschema only if we move to new version of it then I can work on nova using the v7 validator from jsonschema. but moving to new jsonschema still have v4 draft which is used in nova so no backward incompatible change due to that.23:16
gmannsean-k-mooney: as summary, I can work on that part later once jsonschema version is bumped 23:17

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!