[CONTROLLER-1205] Restconf RPC: Response data not inclosed in "output" container Created: 13/Mar/15  Updated: 19/Oct/17  Resolved: 19/Mar/15

Status: Resolved
Project: controller
Component/s: restconf
Affects Version/s: Post-Helium
Fix Version/s: None

Type: Bug
Reporter: Vratko Polak Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All

External issue ID: 2841

 Description   

There were changes to Lithium restconf, and after OPNFLWPLUG-378 was fixed this one become visible.

Using add-lsp call from bgpcep project https://wiki.opendaylight.org/view/BGP_LS_PCEP:Programmer_Guide#Creating_LSP_2
on older Lithium (and Helium) builds was returning
JSON:
{"output":{}}
XML:
<?xml version="1.0" encoding="UTF-8" standalone="no"?><output xmlns="urn:opendaylight:params:xml:ns:yang:topology:pcep"/>

But currently:
JSON:
{}
XML:
<zdef648384929:data xmlns:zdef648384929="urn:ietf:params:xml:ns:netconf:base:1.0"></zdef648384929:data>

There was no significant change in PCEP code, so this is a resconf issue and https://tools.ietf.org/html/draft-bierman-netconf-restconf-02#section-5.4.2
implies this is a bug, not a feature.

 Comments   
Comment by Dana Kutenicsova [ 16/Mar/15 ]

Due to previous experience, increasing to blocker right away, as all PCEP tests fail.

Comment by Tony Tkacik [ 17/Mar/15 ]

Correct behaviour is to return 204 No Content (and no content)
for the RPCs without output,
so it seems current behaviour and also stable/helium behaviour is buggy.

Comment by Tony Tkacik [ 17/Mar/15 ]

In use case for this specific RPC, returned value
should be
{ "output": {} } for JSON or <output xmlns="urn:opendaylight:params:xml:ns:yang:topology:pcep"/>

Comment by Tony Tkacik [ 17/Mar/15 ]

https://git.opendaylight.org/gerrit/#/c/16684/

Generated at Wed Feb 07 19:54:56 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.