<div dir="ltr"><div>The jsonschema limitation in warlock [1] is removed in master branch but now we need a new release. Looking at the code of this project, is it possible to avoid importing this project and implement the required functionality? Code looks short and easy to be re-implemented (basically what I'm saying is to copy-paste this code into oslo.utils).<br></div><div><br></div><div>[1]<a href="https://github.com/bcwaldon/warlock/issues/64" rel="noreferrer" target="_blank">https://github.com/bcwaldon/warlock/issues/64</a></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Jun 15, 2022 at 2:13 AM Sean Mooney <<a href="mailto:smooney@redhat.com">smooney@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Wed, 2022-06-15 at 00:58 +0100, Sean Mooney wrote:<br>
> On Tue, 2022-06-14 at 18:49 -0500, Ghanshyam Mann wrote:<br>
> > ---- On Tue, 14 Jun 2022 17:47:59 -0500 Thomas Goirand <<a href="mailto:zigo@debian.org" target="_blank">zigo@debian.org</a>> wrote ----<br>
> > > On 6/13/22 00:10, Thomas Goirand wrote:<br>
> > > > Hi,<br>
> > > > <br>
> > > > A few DDs are pushing me to upgrade jsonschema in Debian Unstable. <br>
> > > > However, OpenStack global requirements are still stuck at 3.2.0. Is <br>
> > > > there any reason for it, or should we attempt to upgrade to 4.6.0?<br>
> > > > <br>
> > > > I'd really appreciate if someone (else than me) was driving this...<br>
> > > > <br>
> > > > Cheers,<br>
> > > > <br>
> > > > Thomas Goirand (zigo)<br>
> > > > <br>
> > > <br>
> > > FYI, Nova fails with it:<br>
> > > <a href="https://ci.debian.net/data/autopkgtest/unstable/amd64/n/nova/22676760/log.gz" rel="noreferrer" target="_blank">https://ci.debian.net/data/autopkgtest/unstable/amd64/n/nova/22676760/log.gz</a><br>
> > > <br>
> > > Can someone from the Nova team investigate?<br>
> > <br>
> > Nova failures are due to the error message change (it happens regularly and they change them in most versions)<br>
> > in jsonschema new version. I remember we faced this type of issue previously also and we updated<br>
> > nova tests not to assert the error message but seems like there are a few left which is failing with<br>
> > jsonschema 4.6.0.<br>
> > <br>
> > Along with these error message failures fixes and using the latest jsonschema, in nova, we use<br>
> > Draft4Validator from jsonschema and the latest validator is Draft7Validator so we should check<br>
> > what are backward-incompatible changes in Draft7Validator and bump this too?<br>
> <br>
> well i think the reason this is on 3.2.0 iis nothing to do with nova<br>
> i bumpt it manually in <a href="https://review.opendev.org/c/openstack/requirements/+/845859/" rel="noreferrer" target="_blank">https://review.opendev.org/c/openstack/requirements/+/845859/</a><br>
> <br>
> The conflict is caused by:<br>
> The user requested jsonschema===4.0.1<br>
> tripleo-common 16.4.0 depends on jsonschema>=3.2.0<br>
> rsd-lib 1.2.0 depends on jsonschema>=2.6.0<br>
> taskflow 4.7.0 depends on jsonschema>=3.2.0<br>
> zvmcloudconnector 1.4.1 depends on jsonschema>=2.3.0<br>
> os-net-config 15.2.0 depends on jsonschema>=3.2.0<br>
> task-core 0.2.1 depends on jsonschema>=3.2.0<br>
> python-zaqarclient 2.3.0 depends on jsonschema>=2.6.0<br>
> warlock 1.3.3 depends on jsonschema<4 and >=0.7<br>
> <br>
> <a href="https://zuul.opendev.org/t/openstack/build/06ed295bb8244c16b48e2698c1049be9" rel="noreferrer" target="_blank">https://zuul.opendev.org/t/openstack/build/06ed295bb8244c16b48e2698c1049be9</a><br>
> <br>
> it looks like warlock is clamping it ot less then 4 which is why we are stokc on 3.2.0<br>
glance client seams to be the only real user of this<br>
<a href="https://codesearch.opendev.org/?q=warlock&i=nope&literal=nope&files=&excludeFiles=&repos=" rel="noreferrer" target="_blank">https://codesearch.opendev.org/?q=warlock&i=nope&literal=nope&files=&excludeFiles=&repos=</a><br>
perhaps we could jsut remove the dependcy?<br>
> <br>
> > <br>
> > -gmann<br>
> > <br>
> > > <br>
> > > Cheers,<br>
> > > <br>
> > > Thomas Goirand (zigo)<br>
> > > <br>
> > > <br>
> > <br>
> <br>
<br>
<br>
</blockquote></div>