[#NETCONF-343] Clustering: Follower mount point is not ready despite device's connected status

[NETCONF-343] Clustering: Follower mount point is not ready despite device's connected status Created: 30/Jan/17 Updated: 15/Mar/19 Resolved: 06/Feb/17
Status:	Resolved
Project:	netconf
Component/s:	netconf
Affects Version/s:	None
Fix Version/s:	None

Type:

Bug

Reporter:

Jakub Morvay

Assignee:

Unassigned

Resolution:

Won't Do

Votes:

Labels:

None

Remaining Estimate:

Not Specified

Time Spent:

Not Specified

Original Estimate:

Not Specified

Environment:

Operating System: All
Platform: All

External issue ID:

7699

Description

There is a short period when we can see device connected in netconf topology but followers mountpoints are not ready yet.

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.

Comments

Comment by Tomas Cere [ 06/Feb/17 ]

There is no api contract in place that declares that when connected is written into the datastore, MountPointService will already have a mountpoint registered.
Due to the nature of cds you cant keep this value different on each node depending on status of each node.
You should use the existing MountPointService and DOMMOuntPointService ability to register listeners which give you the local status of the MountPoint.

Generated at Wed Feb 07 20:14:46 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.

[NETCONF-343] Clustering: Follower mount point is not ready despite device's connected status Created: 30/Jan/17 Updated: 15/Mar/19 Resolved: 06/Feb/17