[NETCONF-639] Netconf can confuse action definitions when they have equal name Created: 23/Aug/19 Updated: 16/Mar/20 Resolved: 16/Mar/20 |
|
| Status: | Resolved |
| Project: | netconf |
| Component/s: | netconf |
| Affects Version/s: | None |
| Fix Version/s: | Neon SR3, Magnesium, Sodium SR1 |
| Type: | Bug | Priority: | High |
| Reporter: | Robert Varga | Assignee: | Anna Bencúrová |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
Attempting to invoke actions on the following model:
module conflict {
yang-version 1.1;
namespace "whatever";
container foo {
action xyzzy {
input {
leaf foo {
type string;
}
}
}
}
list bar {
action xyzzy {
input {
leaf bar {
type int8;
}
}
}
}
}
will not reliably, because NetconfMessageTransformer is using only the action name to find the definition – hence it will confuse the two definitions.
|
| Comments |
| Comment by Robert Varga [ 23/Aug/19 ] |
|
Also, the code fails to find the following action:
module action-choice {
choice foo {
container cont {
action bar;
}
}
}
|