This Bug mostly manifests as 404 error in cluster-stress job.

Appearance is quite complicated.
This Bug is not present in Beryllium [0] and it was not present in early Carbon [1]. In Boron, it is present both in only job as 404 [2] and in all job as data without netconf-related entity [3]. But in recent Carbon, the netconf-related entity is present in all job [4], while the only job still leads to 404 [5].

This particular check has 3 minute timeout, so a timing issue is not probable, and karaf.log does not contain anything suspicious.

[0] https://logs.opendaylight.org/releng/jenkins092/netconf-csit-3node-cluster-stress-only-beryllium/25/archives/log.html.gz#s1-s1-t3-k2-k2-k5-k3-k1-k3
[1] https://logs.opendaylight.org/releng/jenkins092/netconf-csit-3node-cluster-stress-only-carbon/3/archives/log.html.gz#s1-s1-t3-k2-k2-k5-k3-k1-k4-k1
[2] https://logs.opendaylight.org/releng/jenkins092/netconf-csit-3node-cluster-stress-only-boron/49/archives/log.html.gz#s1-s1-t3-k2-k1-k5-k3-k1-k3
[3] https://logs.opendaylight.org/releng/jenkins092/netconf-csit-3node-cluster-stress-all-boron/63/archives/log.html.gz#s1-s1-t3-k2-k1-k5-k3-k1-k4-k1
[4] https://logs.opendaylight.org/releng/jenkins092/netconf-csit-3node-cluster-stress-all-carbon/62/archives/log.html.gz#s1-s1-t3-k2-k1-k5-k3-k1-k4-k1
[5] https://logs.opendaylight.org/releng/jenkins092/netconf-csit-3node-cluster-stress-only-carbon/122/archives/log.html.gz#s1-s1-t3-k2-k1-k5-k3-k1-k3