Operating System: All
Platform: All

After replicate the issue and research, the problem its in the Test. Steps need be done as explained on guide https://wiki.opendaylight.org/view/BGP_LS_PCEP:TCP_MD5_Guide.

Test are trying to insert dependency directly doing PUT:
http://localhost:8181/restconf/config/network-topology:network-topology/topology/topology-netconf/node/controller-config/yang-ext:mount/config:modules/module/odl-pcep-impl-cfg:pcep-dispatcher-impl/global-pcep-dispatcher/odl-pcep-impl-cfg:md5-channel-factory

<md5-channel-factory xmlns="urn:opendaylight:params:xml:ns:yang:controller:pcep:impl">
<type xmlns:prefix="urn:opendaylight:params:xml:ns:yang:controller:tcpmd5:netty:cfg">prefix:md5-channel-factory</type>
<name>md5-client-channel-factory</name>
</md5-channel-factory>

But it, need to be approach by doing a PUT of the whole module:
(Further explanation why its required-->NETCONF-30)

http://localhost:8181/restconf/config/network-topology:network-topology/topology/topology-netconf/node/controller-config/yang-ext:mount/config:modules/module/odl-pcep-impl-cfg:pcep-dispatcher-impl/global-pcep-dispatcher/

<module xmlns="urn:opendaylight:params:xml:ns:yang:controller:config">
<type xmlns:x="urn:opendaylight:params:xml:ns:yang:controller:pcep:impl">x:pcep-dispatcher-impl</type>
<name>global-pcep-dispatcher</name>
<pcep-extensions xmlns="urn:opendaylight:params:xml:ns:yang:controller:pcep:impl">
<type xmlns:x="urn:opendaylight:params:xml:ns:yang:controller:pcep:spi">x:extensions</type>
<name>global-pcep-extensions</name>
</pcep-extensions>
<pcep-session-proposal-factory xmlns="urn:opendaylight:params:xml:ns:yang:controller:pcep:impl">
<type xmlns:x="urn:opendaylight:params:xml:ns:yang:controller:pcep">x:pcep-session-proposal-factory</type>
<name>stateful07-proposal</name>
</pcep-session-proposal-factory>
<boss-group xmlns="urn:opendaylight:params:xml:ns:yang:controller:pcep:impl">
<type xmlns:x="urn:opendaylight:params:xml:ns:yang:controller:netty">x:netty-threadgroup</type>
<name>global-boss-group</name>
</boss-group>
<worker-group xmlns="urn:opendaylight:params:xml:ns:yang:controller:pcep:impl">
<type xmlns:x="urn:opendaylight:params:xml:ns:yang:controller:netty">x:netty-threadgroup</type>
<name>global-worker-group</name>
</worker-group>
<md5-channel-factory xmlns="urn:opendaylight:params:xml:ns:yang:controller:pcep:impl">
<type xmlns:x="urn:opendaylight:params:xml:ns:yang:controller:tcpmd5:netty:cfg">x:md5-channel-factory</type>
<name>md5-client-channel-factory</name>
</md5-channel-factory>
<md5-server-channel-factory xmlns="urn:opendaylight:params:xml:ns:yang:controller:pcep:impl">
<type xmlns:x="urn:opendaylight:params:xml:ns:yang:controller:tcpmd5:netty:cfg">x:md5-server-channel-factory</type>
<name>md5-server-channel-factory</name>
</md5-server-channel-factory>
</module>

Clarifications with respect to "tcpmd5user" test suite.

There is a real NETCONF-30 which can have many consequences. BGPCEP-277 documents one consequence, but it needs a non-standard (as in different from wiki) workflow to hit 3753.

This suite was using the BGPCEP-277 workflow, and it looked as Tcpmd5 is unusable because of it. Resolved/invalid is there to inform it is not a blocker, and the wiki way works without issues.