[YANGTOOLS-255] Yangtools creates two yang modules in cache/schema for some modules Created: 06/Aug/14 Updated: 10/Apr/22 Resolved: 20/Feb/18 |
|
| Status: | Verified |
| Project: | yangtools |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Giles Heron | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: Mac OS |
||
| External issue ID: | 1498 |
| Description |
|
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. is this expected behaviour? |
| Comments |
| Comment by Maros Marsalek [ 24/Mar/15 ] |
|
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. 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. Please verify with your device and close this issue. |
| Comment by Robert Varga [ 08/Sep/15 ] |
|
I think the problem may be on the NE, which does not advertise the model revision – which is not exactly a conformance issue, as both naming conventions are allowed. Since the revision is not advertised, the schema repository does not know the revision of the model until it parses it – but to do that it needs to download it first, which triggers a writeout. 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. |
| Comment by Robert Varga [ 26/Oct/17 ] |
|
Giles, is this still happening? I think this got fixed along with |