Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Missing/no namespace error in YANG augments with default values #354

Closed
olofhagsand opened this issue Aug 17, 2022 · 0 comments
Closed

Missing/no namespace error in YANG augments with default values #354

olofhagsand opened this issue Aug 17, 2022 · 0 comments

Comments

@olofhagsand
Copy link
Member

This error appeared in 5.8.0.
Error can manifest in several ways. Example symptoms:

  1. On startup or edit of config with the error message on the form:
   <rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
     <rpc-error>
        <error-info>
          <bad-element>enable</bad-element>
       </error-info>
       <error-message>Missing namespace</error-message>
      </rpc-error>
   </rpc-reply>
  1. CLI show config
    xml2ns_recurse: 552: XML error: No namespace associated with ngmap:parameters: No such file or directory

This occurs in YANG constructs on the form:

module example {
  prefix ex;
  container table{
  }
}
module augment {
   prefix aug;
   import example {
      prefix ex;
   }
   augment "/ex:table" {
      container map{
         leaf name{
            type string;
         }
	 leaf enable {
	    type boolean;
	    default true;
         }
      }
   }
}

The augmented part must also have a configured part, such as:

 cli> set table map name x
 cli > show configuration 
Aug 17 16:08:48: xml2ns_recurse: 552: XML error: No namespace associated with aug:enable: No such file or directory

olofhagsand added a commit that referenced this issue Aug 18, 2022
…es](#354)

Tests: ensure all netconf requests with identityref have declared namespaces.
  * This is part of fixing [Yang identityref XML encoding is not general](#90)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant