Hello Dirk,
The issue is there because the syntax for some fields between json schema draft-04 and draft-06/07 has changed. The same issue exists in ironic as well when they switch to jsonschema 3.0.1. The bug and fix have been raised in ironic as well for that. Ref: https://storyboard.openstack.org/#!/story/2005464 patch: https://review.openstack.org/#/c/653060/
The community has decided to use draft-04 for now instead of draft-07 of jsonschema. Since draft-04 is supported for both jsonschema 2.6 and jsonschema 3.0.1, the fix works with that. We plan to fix proliantutils also in the same way as of now.
Regards Nisha
Hello Dirk,
The issue is there because the syntax for some fields between json schema draft-04 and draft-06/07 has changed. The same issue exists in ironic as well when they switch to jsonschema 3.0.1. The bug and fix have been raised in ironic as well for that. /storyboard. openstack. org/#!/ story/2005464 /review. openstack. org/#/c/ 653060/
Ref: https:/
patch: https:/
The community has decided to use draft-04 for now instead of draft-07 of jsonschema. Since draft-04 is supported for both jsonschema 2.6 and jsonschema 3.0.1, the fix works with that. We plan to fix proliantutils also in the same way as of now.
Regards
Nisha