That’s a possibility (for some value of “properly”), but since we don’t know what’s in your modules, it’s hard to say. Generally speaking, if module A augments
/b:foo/b:bar in module B, when module A is compiled, the compiler will load module B and verify that the path
/foo/bar actually exists there (and refers to an augmentable node, not e.g. a leaf or leaf-list). If you then at load time get an error saying that
/foo/bar in module B can’t be found, it means that the compiled B.fxs doesn’t have that node.
One possible reason is that module B was changed and the
bar node was removed, but module A was not compiled with the new version of module B. Another is that B wasn’t actually changed, but a module C that removes
deviate not-supported is used when compiling B, but not when compiling A. Looking at your specific case, there is no node called
vrf-label in the current version of
ietf-network-instance (at https://tools.ietf.org/html/draft-ietf-rtgwg-ni-model-12). Perhaps it existed in an earlier version, and you still have that version in the path when compiling eci-bgp-l3vpn-aug, while ietf-network-instance.fxs was compiled from the current version?
By the way, posting a followup re-asking for an answer just a few hours after posting your question might be considered bad form in a forum like this, and is in any case not likely to get you an answer any sooner.