https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/YANGTOOLS-889 yangtools <p>given </p> <p> </p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java"> <span class="code-keyword">import</span> openconfig-bgp-policy { prefix bgppol; } </pre> </div></div> <p>and using</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java">  augment /rpol:routing-policy/rpol:policy-definitions/rpol:policy-definition/rpol:statements/rpol:statement/rpol:actions/bgp-pol:bgp-actions { </pre> </div></div> <p> </p> <p>Notice bgpol != bgp-pol</p> <p>won't produce any error or complain. Whether this doesn't seems to have any negative impact,</p> <p>it should be addressed correctly.</p> <p>Code Example</p> <p><a href="https://git.opendaylight.org/gerrit/#/c/73697/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/73697/</a></p> YANGTOOLS-889

Using wrong prefix on augmentation not caught

Bug Medium Resolved Done Robert Varga Claudio David Gasparini Tue, 3 Jul 2018 10:45:32 +0000 Tue, 31 Jul 2018 11:48:29 +0000 Tue, 10 Jul 2018 07:23:15 +0000 2.0.7 2.0.8 2.0.6.1 0 2 <p>No issue is observed, but I would expect an alert or error when using wrong prefix.</p> <p>This boils down to SourceSpecificContext.getFromLocalStorage() looking also into imported modules' storage – and finding a match provided by openconfig-bgp-policy.yang's prefix statement. That is wrong and seems to contradict the intended behavior of the ImportPrefixToModuleCtx.</p> <p>As it turns out the namespace behaviour of ImportPrefixToModuleCtx is wrong, as it should not be NamespaceBehaviour.sourceSpecific(), but limited to root statement.</p> Development Rank 0|i03gcf: