[NETCONF-309] Inconsistent connection-status and mountpoint availability Created: 26/Oct/16  Updated: 15/Mar/19  Resolved: 27/Oct/16

Status: Resolved
Project: netconf
Component/s: netconf
Affects Version/s: None
Fix Version/s: None

Type: Bug
Reporter: Michal Rehak Assignee: Unassigned
Resolution: Cannot Reproduce Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All

Attachments: Text File netconf-bug.txt    
External issue ID: 7036

 Description   

When connecting to netconf-testtool with a custom capability then connection-status is connected but mountpoint is not available.

This happens when capabilities are preconfigured (override=true). It seems that netconf-monitoring makes it all work once it is preconfigured too.

See scenario details in attached file.
(element <yang-module-capabilities> is child of network-topology:node element)

 Comments   
Comment by Michal Rehak [ 26/Oct/16 ]

Attachment netconf-bug.txt has been added with description: connection-state inconsistence scenario detail

Comment by Rudolf Brisuda [ 27/Oct/16 ]

The presented scenarios are all correct. Scenario A presents situation when no capabilities are included, so it includes default caps. Device with no capabilities is not usable. Also if you want override capabilities and you do not include monitoring, mount point is not reachable (case B and C).

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