[NETCONF-1144] Referencing nonexistent schemas on branches 4 and 5 Created: 30/Aug/23  Updated: 09/Jan/24  Resolved: 08/Nov/23

Status: Resolved
Project: netconf
Component/s: restconf-openapi
Affects Version/s: None
Fix Version/s: 4.0.9, 5.0.8

Type: Bug Priority: Medium
Reporter: Šimon Ukuš Assignee: Samuel Schneider
Resolution: Done Votes: 0
Labels: pt
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: JPEG File incorrect-schema-ref-on-5-branch.jpg    
Issue Links:
Relates
relates to NETCONF-1133 Incorrect schema reference in root po... Resolved

 Description   

When creating references to schemas we create reference to the schema within the json mime type, which correctly references an existing schema. We do the same for xml mime type except we add the "_xml" suffix.

This is problem as we are not creating schema with such name, so we end up with
incorrect references, thus with incorrect request/response body.

This problem with "_xml" schema references is not present on master branch and neither on the branch 6, but affects branches 4 and 5.

Possible solutions are:

  • create the extra schemas that are not created, but are being referenced
    • might be as easy as just creating schema with the "_xml" suffix and make it reference the non-suffixed schema
    • this however will increase our already high number of schemas
  • apply change from master that removes "_xml" and "_post" suffixed schemas

 

NOTE:

This is different issue than https://jira.opendaylight.org/browse/NETCONF-1133 , which also deals incorrect schema reference, but that deals with the reference in root POST operation, which affects all branches (this issue affects only branches 4 and 5).

 



 Comments   
Comment by Samuel Schneider [ 12/Oct/23 ]

This issue was resolved by Cherry picks:
4.0.x : https://git.opendaylight.org/gerrit/c/netconf/+/107568
5.0.x : https://git.opendaylight.org/gerrit/c/netconf/+/107567

As was proposed by possible solution #2.

Generated at Wed Feb 07 20:16:47 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.