Getting configuration using Netconf renders invalid data - for instance, a message like

<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="1">
<get-config>
<source>
<running/>
</source>
</get-config>
</rpc>

yields a configuration containing among others

<module>
<prefix:type xmlns:prefix="urn:opendaylight:params:xml:ns:yang:controller:logback:config">prefix:logback</prefix:type>
<prefix:name xmlns:prefix="urn:opendaylight:params:xml:ns:yang:controller:logback:config">singleton</prefix:name>
....
</module>

Note the namespace of the "type" and "name" elements - I believe it should belong to the config module, not config-logging.

Likely related is that the file controller.currentconfig.xml created in case of a configuration change is invalid as well, and as a result, starting ODL generates:

Exception in thread "config-pusher" java.lang.IllegalStateException: Failed to send edit-config for configuration ....
at org.opendaylight.controller.netconf.persist.impl.ConfigPusher.sendRequestGetResponseCheckIsOK(ConfigPusher.java:245)
at org.opendaylight.controller.netconf.persist.impl.ConfigPusher.pushConfig(ConfigPusher.java:196)
at org.opendaylight.controller.netconf.persist.impl.ConfigPusher.pushConfigWithConflictingVersionRetries(ConfigPusher.java:88)
at org.opendaylight.controller.netconf.persist.impl.ConfigPusher.pushConfigs(ConfigPusher.java:69)
at org.opendaylight.controller.netconf.persist.impl.osgi.ConfigPersisterActivator$InnerCustomizer$1.run(ConfigPersisterActivator.java:156)
at java.lang.Thread.run(Thread.java:744)
Caused by: NetconfDocumentedException{message=One element type expected in XmlElement

, errorType=application, errorTag=invalid_value, errorSeverity=error, errorInfo={}}
at org.opendaylight.controller.netconf.util.xml.XmlElement.getOnlyChildElement(XmlElement.java:239)
at org.opendaylight.controller.netconf.confignetconfconnector.mapping.config.Services.fromXml(Services.java:92)
....