[YANGTOOLS-817] Deviate replace of undeclared config substatement fails Created: 04/Oct/17 Updated: 10/Apr/22 Resolved: 20/Nov/17 |
|
| Status: | Verified |
| Project: | yangtools |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 2.0.0, 1.2.1 |
| Type: | Bug | ||
| Reporter: | Igor Foltin | Assignee: | Igor Foltin |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| External issue ID: | 9244 |
| Description |
|
The problem looks like this: We want to replace a config substatement which is not explicitly declared in the target node using deviate replace. YANG statement parser throws an exception as it cannot find the config substatement in the target node. RFC6020/RFC7950 states that if a node does not have a config substatement declared within it, the config value is set according to its parent node. If the parent node does not declare a config, then it defaults to true. The question is - do we want to add an implicit config substatement in case it is not declared explicitly or do we prefer using deviate add instead of deviate replace in this particular case? |
| Comments |
| Comment by Igor Foltin [ 17/Oct/17 ] |
|
Fix on master: https://git.opendaylight.org/gerrit/#/c/64389/ |
| Comment by Igor Foltin [ 19/Oct/17 ] |
|
Nitrogen fix: https://git.opendaylight.org/gerrit/#/c/64517/ |