Any attempt to add a BGP peer through RESTCONF will be rejected.

Steps to reproduce:

1. ODL_ROOT=<where_yourODL_installation_lives>
2. Boot ODL.
3. Install features "odl-restconf", "odl-bgppcep-bgp-all" and "odl-netconf-connector-all".
4. Wait for ODL to fully load (run "top" in another console and wait until CPU usage of the massive Java process stays below 5%).
5. curl -u 'admin:admin' -X POST -H "Content-Type:application/xml" -d '
<module xmlns="urn:opendaylight:params:xml:ns:yang:controller:config">
<type xmlns:prefix="urn:opendaylight:params:xml:ns:yang:controller:bgp:rib:impl">prefix:bgp-peer</type>
<name>example-bgp-peer</name>
<peer-role>Ibgp</peer-role>
<host>127.0.0.201</host>
<holdtimer>180</holdtimer>
</module>
' 127.0.0.1:8181/restconf/config/network-topology:network-topology/topology/topology-netconf/node/controller-config/yang-ext:mount/config:modules

You will get the following error from the command in step 5:

{
"errors": {
"error": [

{ "error-type": "protocol", "error-tag":"malformed-message", "error-message":"Error parsing input: Unknown child(ren) node(s) detected, identified by: (urn:opendaylight:params:xml:ns:yang:controller:config)peer-role, in: list module" }

]
}
}

No errors will be logged into the logs.

Note also that I suspect this might be just a different symptom of CONTROLLER-1280 but I am not sure. The two paths to the breakage and the two symptoms are quite different, the only thing that these two have in common is than in both a BGP peer configuration is involved. To increase clarity and prevent confusion I logged these two symptoms as 2 separate bugs.