standard edit-config fails when module augmenting base netconf has been retrieved from device

When a yang module that augments the base netconf edit-config rpc with an "output" statement is retrieved by ODL from a device, edit-config operations sent from ODL to this device fail, even if the augmentation is not used. It seems the "output" statement in the yang module causes ODL to not recognize a standard "ok" rpc-reply sent from the device in response to the edit-config rpc. Instead ODL reports an error and restarts the netconf session. Here is the related entry in karaf.log:

java.lang.IllegalArgumentException: Failed to parse RPC response [rpc-reply: null]

Caused by: javax.xml.stream.XMLStreamException: Schema for node with name ok and namespace urn:ietf:params:xml:ns:netconf:base:1.0 does not exist at AbsoluteSchemaPath{path=[(urn:ietf:params:xml:ns:netconf:base:1.0?revision=2011-06-01)edit-config, (urn:ietf:params:xml:ns:netconf:base:1.0?revision=2011-06-01)output]}