cinder volume fails to report in if jsonschema doesn't match what it was compiled with

[Sean Dague]

This is a holding bug for the fact that tempest had updated to a lesser version of jsonschema, which causes "interesting" fails during grenade upgrade (though not in the main gate).

[Sean Dague (sdague)]

I realize this isn't quite a ci problem, but it's requirements related, so I want to leave it here for now.

[Sean Dague (sdague)]

Ok, the crux of the problem:

glance doesn't do global requirements, it specifies jsonschema without a verison, and installs version 2.

cinder has a shadow dependency on jsonschema, so compiles entry points against 2.

tempest added jsonschema as an explicit requirement >=0.7,!=1.4.0,<2 (yes... that's the global requirement), it slid in at the end. Now cinder doesn't work.

now... why this only broke in grenade... I still don't understand.

[Clark Boylan (cboylan)]

Sean Dague fixed this by overhauling how global requirements are applied to projects during testing (projects are forced to use the global requirements during integration testing).