[BGPCEP-697] Data change counter not ready with tell-based protocol Created: 11/Oct/17 Updated: 16/Nov/21 Resolved: 16/Nov/21 |
|
| Status: | Resolved |
| Project: | bgpcep |
| Component/s: | BGP |
| Affects Version/s: | Bugzilla Migration |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Vratko Polak | 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 |
||
| External issue ID: | 9271 |
| Description |
|
This is seen in CSIT tests, relevant for Carbon-SR2 candidate validation. After configuration, read of /restconf/operational/data-change-counter:data-change-counter returns [0] 404 with: ]}} Note that the same suite is also running with ask-based protocol, when the read succeeds [1]. There is a hard reset between the suites. I have been trying to reproduce this on Sandbox with a simplified testplan, both on As on Releng, Verify_Data_Change_Counter_Ready test case if failing consistently [4], mu current hypothesis is that this failure is somehow caused by the previous suite, even though that suite occasionally passes [5]. More investigation is needed. [0] https://logs.opendaylight.org/releng/jenkins092/bgpcep-csit-1node-periodic-bgp-ingest-all-carbon/418/log.html.gz#s1-s12-t6-k2-k1-k2 |
| Comments |
| Comment by Claudio David Gasparini [ 16/Jan/18 ] |
|
Tomas could you check if this still valid please |
| Comment by Robert Varga [ 16/Nov/21 ] |
|
No feedback on whether this is still relevant. If this happens again we can reopen. |