Operating System: All
Platform: All

Gerrit Patch:
https://git.opendaylight.org/gerrit/#/c/45073/

Some PATCH edit operations do bot work properly on mounted devices due to https://bugs.opendaylight.org/show_bug.cgi?id=6681

Gerrit patch for old restconf is waiting for review:
https://git.opendaylight.org/gerrit/#/c/45073/

Gerrit patch for new restconf: https://git.opendaylight.org/gerrit/#/c/46123/

To work with transaction chains on mount point s you need: https://git.opendaylight.org/gerrit/#/c/45575/

adaptation for Beryllium:
https://git.opendaylight.org/gerrit/#/c/46533/

Will this be in Beryllium-SR4 and Boron-SR1?

(In reply to Giles Heron from comment #8)
> Will this be in Beryllium-SR4 and Boron-SR1?

Hi Giles,

This is in both releases.

Regards,

Jakub Toth

do you have any examples of using this to edit a mounted resource?

See for example: https://lists.opendaylight.org/pipermail/netconf-dev/2016-October/000718.html

yup - I saw that. Still wasn't able to make it work

might start by trying a non-mounted model

Yes, try first non-mounted, mounted is the same, only URi changes.

I could see below challenges while executing HTTP PATCH on a netconf mount point.

Version : Boron
Issue reg : HTTP PATCH
Module : ietf-yang-patch.yang

1. Is yang patch not supported to change configuaration datastore on mount point ?
2. If this is supported on mount point, Is ODL controller expecting ietf-yang-patch module from mount point ? I don’t see this module under “schema” directory of ODL controller.
3. When we tried to emit this module from mount point we could see import failing for “import ietf-restconf

”, but still it is listed under available-capability for mount point and seeing below error while trying to add config in yang-patch format.

HTTP PATCH method:

PATCH /restconf/config/network-topology:network-topology/topology/topology-netconf/node/device1/yang-ext:mount/ietf-yang-patch:yang-patch HTTP/1.1
Host: 10.209.1.8:8181

Headers:

Accept: application/yang.patch-status+xml
Content-Type: application/yang.patch+json

Body:

{
"ietf-yang-patch:yang-patch": {
"patch-id": "test",
"edit": {
"edit-id": "edit1",
"operation": "create",
"target": "/interfaces",
"interface": {
"name": "ge-0/0/0",
"unit": {
"name": "0",
"family": {
"inet": {
"address":

}
}
}
}
}
}
}

Response:

{
"errors": {
"error": [

]
}
}

karaf Log:

2017-04-28 14:36:59,488 | WARN | ssing-executor-1 | NetconfDevice | 263 - org.opendaylight.netconf.sal-netconf-connector - 1.4.1.Boron-SR
1 | RemoteDevice

: Trying to build schema context from [RevisionSourceIdentifier [name=show-version@2017-01-01]]
2017-04-28 14:36:59,494 | DEBUG | ssing-executor-1 | NetconfDevice | 263 - org.opendaylight.netconf.sal-netconf-connector - 1.4.1.Boron-SR
1 | RemoteDevice

: Creating master data broker for device
2017-04-28 14:36:59,496 | DEBUG | ssing-executor-1 | NetconfDeviceSalProvider | 263 - org.opendaylight.netconf.sal-netconf-connector - 1.4.1.Boron-SR
1 | RemoteDevice

: Netconf session initiated, starting keepalives
2017-04-28 14:36:59,497 | DEBUG | lt-dispatcher-55 | NetconfNodeActor | 267 - org.opendaylight.netconf.topology-singleton - 1.1.1.Boron-SR1 |
RemoteDevice

: Scheduling next keepalive in 120 SECONDS
2017-04-28 14:36:59,497 | INFO | ssing-executor-1 | NetconfDevice | 263 - org.opendaylight.netconf.sal-netconf-connector - 1.4.1.Boron-SR
1 | RemoteDevice

: Update device state transaction DOM-CHAIN-65-1 merging operational data started.
2017-04-28 14:36:59,498 | TRACE | dispatcher-58809 | NetconfDeviceTopologyAdapter | 263 - org.opendaylight.netconf.sal-netconf-connector - 1.4.1.Boron-SR
1 | RemoteDevice

: Committing Transaction update:DOM-CHAIN-65-1
2017-04-28 14:36:59,499 | TRACE | ommitFutures-211 | NetconfDeviceTopologyAdapter | 263 - org.opendaylight.netconf.sal-netconf-connector - 1.4.1.Boron-SR
1 | RemoteDevice

: Transaction(update) DOM-CHAIN-65-1 SUCCESSFUL
2017-04-28 14:37:26,077 | TRACE | p219366924-80317 | BrokerFacade | 269 - org.opendaylight.netconf.sal-rest-connector - 1.4.1.Boron-SR1 |
Read OPERATIONAL via Restconf: /(urn:TBD:params:xml:ns:yang:network-topology?revision=2013-10-21)network-topology/topology/topology[

]
2017-04-28 14:37:26,077 | DEBUG | p219366924-80317 | BrokerFacade | 269 - org.opendaylight.netconf.sal-rest-connector - 1.4.1.Boron-SR1 |
Reading result data from transaction.
2017-04-28 14:37:47,617 | TRACE | ssing-executor-8 | KeepaliveSalFacade | 263 - org.opendaylight.netconf.sal-netconf-connector - 1.4.1.Boron-SR
1 | RemoteDevice

: Sending message <rpc message-id="m-285" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<get-config>
<source>

Hi

Yang PATCH is supported on mount points in latest Boron (SR-3).

message:

{
  "errors": {
    "error": [
     

    ]
  }
}

wants to tell you that module "ietf-yang-patch" does not exist behind mount point (its different bug solved in next releases:
https://git.opendaylight.org/gerrit/#/c/52724/).

ietf-yang-patch describes Yang PATCH data message structure, it is not located on mount point or controller itself.
I do not understand why you want to use it.
Try to use another module which you are sure is present behind mount point.

Regards

See examples:
https://wiki.opendaylight.org/view/OpenDaylight_Controller:MD-SAL:Restconf

Just change URI to point to your mount point.