Mark, I have glanceclient 0.9.0 installed.
Thanks, MATT RIEDEMANN Advisory Software Engineer Cloud Solutions and OpenStack Development Phone: 1-507-253-7622 | Mobile: 1-507-990-1889 E-mail: mrie...@us.ibm.com 3605 Hwy 52 N Rochester, MN 55901-1407 United States From: Mark Washenberger <mark.washenber...@markwash.net> To: OpenStack Development Mailing List <openstack-dev@lists.openstack.org>, Date: 07/17/2013 01:07 PM Subject: Re: [openstack-dev] [glance] need to pin jsonschema version for glance? Actually, when I build out a virtual environment and install python-glanceclient, I get jsonschema 2.0.0. So maybe the problem is elsewhere? I also get python-glanceclient 0.9.0, but I notice that tempest requires python-glanceclient >0.5.0 ( https://github.com/openstack/tempest/blob/master/requirements.txt#L11 ). What version of python-glanceclient do you have installed in the environment where there is a problem? On Wed, Jul 17, 2013 at 9:52 AM, Mark Washenberger < mark.washenber...@markwash.net> wrote: On Wed, Jul 17, 2013 at 7:16 AM, Matt Riedemann <mrie...@us.ibm.com> wrote: I recently synched up on the latest glance and ran tempest on my RHEL 6.3 box and the image v2 tests all started failing due to json schema validation errors: http://paste.openstack.org/show/40684/ I found that the version of jsonschema on the system is 0.7, probably because of the dependency from warlock in python-glanceclient: https://github.com/openstack/python-glanceclient/blob/master/requirements.txt#L8 I started looking at what recent changes in glance might be causing the issue and I found this one: https://review.openstack.org/#/c/35134/ As pointed out in the test output from that patch, since there is no version constraint on jsonschema in glance or tempest, it's getting the latest version from pypi (2.0.0 in this case). When I updated my test box to jsonschema 1.3.0, I got past the schema validation error. So this leads me to believe that we need to pin the jsonschema version in glance and tempest to >= 1.3.0. Thoughts? This sounds correct. Another alternative would be to switch back to the "old" syntax and pin < 1.3.0, which sounds like its not really forward progress, but might be easier. Thanks, MATT RIEDEMANN Advisory Software Engineer Cloud Solutions and OpenStack Development Phone: 1-507-253-7622 | Mobile: 1-507-990-1889 E-mail: mrie...@us.ibm.com 3605 Hwy 52 N Rochester, MN 55901-1407 United States _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
<<image/gif>>
<<image/gif>>
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev