[#CONTROLLER-792] Installing some features in karaf causes JSON-encoded RESTCONF responses to be encoded in old format

[CONTROLLER-792] Installing some features in karaf causes JSON-encoded RESTCONF responses to be encoded in old format Created: 09/Sep/14 Updated: 05/May/15 Resolved: 05/May/15
Status:	Resolved
Project:	controller
Component/s:	adsal
Affects Version/s:	Helium
Fix Version/s:	None

Type:

Bug

Reporter:

Jan Medved

Assignee:

Tony Tkacik

Resolution:

Done

Votes:

Labels:

None

Remaining Estimate:

Not Specified

Time Spent:

Not Specified

Original Estimate:

Not Specified

Environment:

Operating System: Mac OS
Platform: Macintosh

External issue ID:

1761

Description

The JSON format in RESTCONF has recently been updated: identifiers no longer contain namespace IDs when not required. But, installing some of the features causes the controller to switch to the old format. The features are:

odl-aaa-all
odl-openflow-nxm-extensions
odl-bgpcep-all
odl-lispflowmapping-all
odl-ttp-all
odl-sfc-all
odl-packetcable-all

Comments

Comment by Tony Tkacik [ 10/Sep/14 ]

Were you using downloaded karaf distribution or locally built-one?

Karaf uses local .m2/repository to search for artefacts and may pick up outdated local artefact,
even if karaf distribution is bundled with newer one in system folder.

This could lead to problem, you were observing - that when you installed features, karaf installed
older restconf from your local .m2/repository.

Comment by Jan Medved [ 10/Sep/14 ]

It happens in both

Comment by Tony Tkacik [ 11/Sep/14 ]

Migration to more state tracking introduced regression
where module name prefix was left out for containers
and lists which were augmented, which was inconsistent
with case augmentations, which were serialized properly.

Draft draft-lhotka-netmod-yang-json-02 allows previous
behaviour (without module names for augmented items),
but that may cause changing textual representation
after conflicting augmentation is introduced,
so we opted to always report module name for top level
items of augmentation, which is also allowed from spec.

SO change did not introduced bug from point of implemented
specification, but did not behaved as intended for
this particular implementation.

Bugfix is in:
https://git.opendaylight.org/gerrit/#/c/11043/

Comment by Carol Sanders [ 05/May/15 ]

This bug is part of the project to Move all ADSAL associated component bugs to ADSAL.

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

[CONTROLLER-792] Installing some features in karaf causes JSON-encoded RESTCONF responses to be encoded in old format Created: 09/Sep/14 Updated: 05/May/15 Resolved: 05/May/15