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-255 yangtools <p>in some instances Yangtools creates two different modules in cache/schema where one module has a revision date in the filename and the other doesn't. The modules are otherwise identical.</p> <p>is this expected behaviour?</p> <p>Operating System: Mac OS<br/> Platform: PC</p> YANGTOOLS-255

Yangtools creates two yang modules in cache/schema for some modules

Bug Verified Done Unassigned Giles Heron Wed, 6 Aug 2014 22:42:03 +0000 Sun, 10 Apr 2022 18:35:14 +0000 Tue, 20 Feb 2018 10:36:56 +0000 0 4 <p>It all depends on how does the remote device report the models. It is possible if a remote device reports yang model with 2 different revisions but for get-schema it returns the same yang file. Netconf connector has to download both of them since it does not know what the content would be.</p> <p>So it is expected if the device reports the models that way. This should be verified in your netconf device because I dont think there is any issue in ODL's netconf connector.</p> <p>Please verify with your device and close this issue.</p> <p>I think the problem may be on the NE, which does not advertise the model revision &#8211; which is not exactly a conformance issue, as both naming conventions are allowed.</p> <p>Since the revision is not advertised, the schema repository does not know the revision of the model until it parses it &#8211; but to do that it needs to download it first, which triggers a writeout.</p> <p>This problem can actually be larger, as we should somehow enforce the consistency of the file name and the module/revision statements contained in it. That means that the cache should only be populated once the model has been parsed successfully.</p> <p>Giles, is this still happening?</p> <p>I think this got fixed along with <a href="https://jira.opendaylight.org/browse/YANGTOOLS-769" title="Log file is filled up Provided module name * does not match actual text *, corrected" class="issue-link" data-issue-key="YANGTOOLS-769"><del>YANGTOOLS-769</del></a> &#8211; I will close it for now, feel free to reopen if you encounter it again.</p> Development External issue ID 1498 External issue URL Issue Type Rank 0|i0263j: