https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/NETCONF-343 netconf <p>There is a short period when we can see device connected in netconf topology but followers mountpoints are not ready yet.</p> <p>Leader updates device connection status after he successfully mounts a device. Followers react on this event and try to register mountpoints and it can take some time. The thing is that also other applications can react on this event and they assume the mountpoints are ready also on followers.</p> <p>Operating System: All<br/> Platform: All</p> NETCONF-343

Clustering: Follower mount point is not ready despite device's connected status

Bug Resolved Won't Do Unassigned Jakub Morvay Mon, 30 Jan 2017 07:24:47 +0000 Fri, 15 Mar 2019 22:22:35 +0000 Mon, 6 Feb 2017 11:45:16 +0000 netconf 0 1 <p>There is no api contract in place that declares that when connected is written into the datastore, MountPointService will already have a mountpoint registered.<br/> Due to the nature of cds you cant keep this value different on each node depending on status of each node.<br/> You should use the existing MountPointService and DOMMOuntPointService ability to register listeners which give you the local status of the MountPoint.</p> Development External issue ID 7699 External issue URL Rank 0|i01xyf: