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

get-schema returns data element with incorrect namespace #10

Closed
GoogleCodeExporter opened this issue Jun 11, 2015 · 1 comment
Closed

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
1. Issue a get-schema rpc. 
<rpc message-id="m-0" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<get-schema xmlns="urn:ietf:params:xml:ns:yang:ietf-netconf-monitoring">
<format>yang</format>
<identifier>ietf-netconf-acm</identifier>
<version>2012-02-22</version>
</get-schema>
</rpc>
2. Wait for result rpc


What is the expected output? What do you see instead?

Expected response is rpc-reply conforming to the ietf-netconf-monitoring, with 
namespace urn:ietf:params:xml:ns:yang:ietf-netconf-monitoring.

Incorrect returned value was:

<?xml version="1.0" encoding="UTF-8"?>
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="m-0">
  <data xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">module "ietf-netconf-acm" {
  namespace "urn:ietf:params:xml:ns:yang:ietf-netconf-acm";
  prefix "nacm";
  ...

Which contains a data element with namespace 
urn:ietf:params:xml:ns:netconf:base:1.0.
The correct namespace should be 
urn:ietf:params:xml:ns:yang:ietf-netconf-monitoring.



Build on master

Please provide any additional information below.

Original issue reported on code.google.com by tonydam...@gmail.com on 27 Feb 2014 at 1:02

@GoogleCodeExporter
Copy link
Author

Moved to libnetconf issue tracker - 
https://code.google.com/p/libnetconf/issues/detail?id=32

Original comment by rkre...@cesnet.cz on 27 Feb 2014 at 1:45

  • Changed state: Invalid

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