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

edit-config does not work #1

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

edit-config does not work #1

GoogleCodeExporter opened this issue Jun 11, 2015 · 1 comment

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
1) netconf-client - connect to server
2) user-rpc with this:
<edit-config>
<target>
<running/>
</target>
<config>
<comet-testers xmlns="http://cesnet.cz/ns/yang/comet-tester">
<comet-tester>
<interface-id>0</interface-id>
<statistics>
<enabled>false</enabled>
</statistics>
</comet-tester>
</comet-testers>
</config>
</edit-config>

OR
edit-config with:
<comet-testers xmlns="http://cesnet.cz/ns/yang/comet-tester">
<comet-tester>
<interface-id>0</interface-id>
<statistics>
<enabled>false</enabled>
</statistics>
</comet-tester>
</comet-testers>


What is the expected output? What do you see instead?
NETCONF error: operation-failed (application) - The request requires a resource 
that already is in use.

Please use labels and text to provide additional information.
get, get-config works correctly

Original issue reported on code.google.com by tom.cejka@gmail.com on 21 Aug 2012 at 2:31

@GoogleCodeExporter
Copy link
Author

This might be (and probably is) problem of netconf server build on the library 
thus I suggest reporting this issue to server developers first.
If you are sure this is library bug, please post minimal example using library 
which is failing within edit-config processing.

Original comment by david.kupka@gmail.com on 22 Aug 2012 at 8:25

  • 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