NETCONF fails to ignore modules with incorrect submodule dates and gets stuck "connecting"

we have a case where a NETCONF Server erroneously reports a different revision date for submodules than for modules. The submodules are actually correct - and have the same revision date as the modules - but get-schema reports the date of the previous revision.

I would expect ODL to fail to mount any such modules, but to continue mounting other modules and for the NETCONF server to reach the "connected" state.

Logs attached.