Test Statistics

Total Statistics
Total
Pass
Fail
Skip
Elapsed
Pass / Fail / Skip
All Tests
1404892001:02:46
Statistics by Tag
Total
Pass
Fail
Skip
Elapsed
Pass / Fail / Skip
critical
402416000:26:49
https://bugs.opendaylight.org/show_bug.cgi?id=4968
16016000:06:11
https://bugs.opendaylight.org/show_bug.cgi?id=5761
707000:07:06
https://bugs.opendaylight.org/show_bug.cgi?id=5762
404000:02:43
https://bugs.opendaylight.org/show_bug.cgi?id=6067
404000:04:03
Statistics by Suite
Total
Pass
Fail
Skip
Elapsed
Pass / Fail / Skip
netconf-clustering.txt
1404892001:03:41
netconf-clustering . txt . CRUD
261115000:05:02
netconf-clustering . txt . Bug8086
261115000:05:02
netconf-clustering . txt . Restart Odl With Tell Based False
321000:06:30
netconf-clustering . txt . Entity
17215000:08:56
netconf-clustering . txt . Restart Odl With Tell Based False
321000:06:33
netconf-clustering . txt . Outages
22814000:17:32
netconf-clustering . txt . Entity
17215000:08:55
netconf-clustering . txt . CRUD
261016000:05:11

Test Execution Errors

20250324 22:48:09.857 WARN Retrying (RetryAdapter(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7fd531375150>: Failed to establish a new connection: [Errno 111] Connection refused')': /rests/data/network-topology:network-topology?content=nonconfig
20250324 22:48:10.058 WARN Retrying (RetryAdapter(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7fd530306590>: Failed to establish a new connection: [Errno 111] Connection refused')': /rests/data/network-topology:network-topology?content=nonconfig
20250324 22:48:10.461 WARN Retrying (RetryAdapter(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7fd531342e10>: Failed to establish a new connection: [Errno 111] Connection refused')': /rests/data/network-topology:network-topology?content=nonconfig
20250324 22:48:14.459 WARN Retrying (RetryAdapter(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7fd5302c2110>: Failed to establish a new connection: [Errno 111] Connection refused')': /rests/data/network-topology:network-topology/topology=topology-netconf/node=netconf-test-device?content=nonconfig
20250324 22:48:14.660 WARN Retrying (RetryAdapter(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7fd5302c3c50>: Failed to establish a new connection: [Errno 111] Connection refused')': /rests/data/network-topology:network-topology/topology=topology-netconf/node=netconf-test-device?content=nonconfig
20250324 22:48:15.063 WARN Retrying (RetryAdapter(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7fd530a9c1d0>: Failed to establish a new connection: [Errno 111] Connection refused')': /rests/data/network-topology:network-topology/topology=topology-netconf/node=netconf-test-device?content=nonconfig
20250324 22:48:16.108 WARN Retrying (RetryAdapter(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7fd5300bd110>: Failed to establish a new connection: [Errno 111] Connection refused')': /rests/data/network-topology:network-topology/topology=topology-netconf/node=netconf-test-device?content=nonconfig
20250324 22:48:16.309 WARN Retrying (RetryAdapter(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7fd531389b50>: Failed to establish a new connection: [Errno 111] Connection refused')': /rests/data/network-topology:network-topology/topology=topology-netconf/node=netconf-test-device?content=nonconfig
20250324 22:48:16.712 WARN Retrying (RetryAdapter(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7fd531392790>: Failed to establish a new connection: [Errno 111] Connection refused')': /rests/data/network-topology:network-topology/topology=topology-netconf/node=netconf-test-device?content=nonconfig
20250324 22:48:17.753 WARN Retrying (RetryAdapter(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7fd530a9b750>: Failed to establish a new connection: [Errno 111] Connection refused')': /rests/data/network-topology:network-topology/topology=topology-netconf/node=netconf-test-device?content=nonconfig
20250324 22:48:17.955 WARN Retrying (RetryAdapter(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7fd530a92110>: Failed to establish a new connection: [Errno 111] Connection refused')': /rests/data/network-topology:network-topology/topology=topology-netconf/node=netconf-test-device?content=nonconfig
20250324 22:48:18.357 WARN Retrying (RetryAdapter(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7fd530a912d0>: Failed to establish a new connection: [Errno 111] Connection refused')': /rests/data/network-topology:network-topology/topology=topology-netconf/node=netconf-test-device?content=nonconfig
20250324 22:48:19.403 WARN Retrying (RetryAdapter(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7fd5308c6490>: Failed to establish a new connection: [Errno 111] Connection refused')': /rests/data/network-topology:network-topology/topology=topology-netconf/node=netconf-test-device?content=nonconfig
20250324 22:48:19.604 WARN Retrying (RetryAdapter(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7fd5308c7ad0>: Failed to establish a new connection: [Errno 111] Connection refused')': /rests/data/network-topology:network-topology/topology=topology-netconf/node=netconf-test-device?content=nonconfig
20250324 22:48:20.006 WARN Retrying (RetryAdapter(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7fd5308c6c10>: Failed to establish a new connection: [Errno 111] Connection refused')': /rests/data/network-topology:network-topology/topology=topology-netconf/node=netconf-test-device?content=nonconfig
20250324 22:48:21.047 WARN Retrying (RetryAdapter(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7fd53092a2d0>: Failed to establish a new connection: [Errno 111] Connection refused')': /rests/data/network-topology:network-topology/topology=topology-netconf/node=netconf-test-device?content=nonconfig
20250324 22:48:21.248 WARN Retrying (RetryAdapter(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7fd53092ae10>: Failed to establish a new connection: [Errno 111] Connection refused')': /rests/data/network-topology:network-topology/topology=topology-netconf/node=netconf-test-device?content=nonconfig
20250324 22:48:21.650 WARN Retrying (RetryAdapter(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7fd53093d410>: Failed to establish a new connection: [Errno 111] Connection refused')': /rests/data/network-topology:network-topology/topology=topology-netconf/node=netconf-test-device?content=nonconfig
20250324 22:48:22.699 WARN Retrying (RetryAdapter(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7fd530953650>: Failed to establish a new connection: [Errno 111] Connection refused')': /rests/data/network-topology:network-topology/topology=topology-netconf/node=netconf-test-device?content=nonconfig
20250324 22:48:22.901 WARN Retrying (RetryAdapter(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7fd530951090>: Failed to establish a new connection: [Errno 111] Connection refused')': /rests/data/network-topology:network-topology/topology=topology-netconf/node=netconf-test-device?content=nonconfig

Test Execution Log

01:03:41.144 SUITE netconf-clustering.txt
Full Name: netconf-clustering.txt
Start / End / Elapsed: 20250324 22:15:52.293 / 20250324 23:19:33.437 / 01:03:41.144
Status: 140 tests total, 48 passed, 92 failed, 0 skipped
00:05:02.476 SUITE CRUD
Full Name: netconf-clustering.txt.CRUD
Documentation:

netconf clustered CRUD test suite.

Copyright (c) 2016 Cisco Systems, Inc. and others. All rights reserved.

This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html

Perform basic operations (Create, Read, Update and Delete or CRUD) on device data mounted onto a netconf connector and see if they work.

The suite recognizes 3 nodes, "CONFIGURER" (the node that configures the device at the beginning and then deconfigures it at the end), "SETTER" (the node that manipulates the data on the device) and "CHECKER" (the node that checks the data on the device). The configured device and the results of each data operation on it is expected to be visible on all nodes so after each operation three test cases make sure they can see the result on their respective nodes.

The 3 nodes are configured by placing "node1", "node2" or "node3" into the node1, node2 and node3 to make the node a "CONFIGURER", "SETTER" and "CHECKER" respectively. The "nodeX" name refers to the node with its IP address configured with the ${ODL_SYSTEM_X_IP} variable where the "X" is 1, 2 or 3.

The suite checks the integrity of the presence of the device and the data seen on the device only for nodes that have at least one of the roles ("CONFIGURER", "SETTER" and "CHECKER") assigned. A better design would have a "checker list" of sorts and have only one checking test case that runs through the check list and performs the test on each node listed. However this currently has fairly low priority due to Beryllium delivery date so it was left out.
Source: /w/workspace/netconf-csit-3node-clustering-only-scandium/test/csit/suites/netconf/clustering/CRUD.robot
Start / End / Elapsed: 20250324 22:15:52.316 / 20250324 22:20:54.792 / 00:05:02.476
Status: 26 tests total, 11 passed, 15 failed, 0 skipped
00:00:06.246 SETUP Setup_Everything  
Documentation:

Initialize SetupUtils, setup everything needed for the test cases.
Start / End / Elapsed: 20250324 22:15:52.820 / 20250324 22:15:59.066 / 00:00:06.246
00:00:00.393 TEARDOWN Teardown_Everything  
Documentation:

Teardown the test infrastructure, perform cleanup and release all resources.
Start / End / Elapsed: 20250324 22:20:54.399 / 20250324 22:20:54.792 / 00:00:00.393
00:00:07.354 TEST Start_Testtool
Full Name: netconf-clustering.txt.CRUD.Start_Testtool
Documentation:

Deploy and start test tool, then wait for all its devices to become online.
Start / End / Elapsed: 20250324 22:15:59.066 / 20250324 22:16:06.420 / 00:00:07.354
Status: PASS
00:00:01.195 TEST Check_Device_Is_Not_Mounted_At_Beginning
Full Name: netconf-clustering.txt.CRUD.Check_Device_Is_Not_Mounted_At_Beginning
Documentation:

Sanity check making sure our device is not there. Fail if found.
Tags: critical
Start / End / Elapsed: 20250324 22:16:06.421 / 20250324 22:16:07.616 / 00:00:01.195
Status: PASS
00:00:00.532 TEST Configure_Device_On_Netconf
Full Name: netconf-clustering.txt.CRUD.Configure_Device_On_Netconf
Documentation:

Make request to configure a testtool device on Netconf connector
Tags: critical
Start / End / Elapsed: 20250324 22:16:07.616 / 20250324 22:16:08.148 / 00:00:00.532
Status: PASS
00:00:00.370 TEST Check_Configurer_Has_Netconf_Connector_For_Device
Full Name: netconf-clustering.txt.CRUD.Check_Configurer_Has_Netconf_Connector_For_Device
Documentation:

Get the list of mounts and search for our device there. Fail if not found.
Tags: critical
Start / End / Elapsed: 20250324 22:16:08.148 / 20250324 22:16:08.518 / 00:00:00.370
Status: PASS
00:00:03.507 TEST Wait_For_Device_To_Become_Visible_For_Configurer
Full Name: netconf-clustering.txt.CRUD.Wait_For_Device_To_Become_Visible_For_Configurer
Documentation:

Wait until the device becomes visible on configurer node.
Start / End / Elapsed: 20250324 22:16:08.518 / 20250324 22:16:12.025 / 00:00:03.507
Status: PASS
00:00:21.088 TEST Wait_For_Device_To_Become_Visible_For_Checker
Full Name: netconf-clustering.txt.CRUD.Wait_For_Device_To_Become_Visible_For_Checker
Documentation:

Wait until the device becomes visible on checker node.
Start / End / Elapsed: 20250324 22:16:12.026 / 20250324 22:16:33.114 / 00:00:21.088
Status: FAIL
Message: Keyword 'Check_Device_Connected' failed after retrying for 20 seconds. The last error was: HTTPError: 409 Client Error: Conflict for url: http://10.30.171.154:8181/rests/data/network-topology:network-topology/topology=topology-netconf/node=netconf-test-device?content=nonconfig
00:00:20.943 TEST Wait_For_Device_To_Become_Visible_For_Setter
Full Name: netconf-clustering.txt.CRUD.Wait_For_Device_To_Become_Visible_For_Setter
Documentation:

Wait until the device becomes visible on setter node.
Start / End / Elapsed: 20250324 22:16:33.114 / 20250324 22:16:54.057 / 00:00:20.943
Status: FAIL
Message: Keyword 'Check_Device_Connected' failed after retrying for 20 seconds. The last error was: HTTPError: 409 Client Error: Conflict for url: http://10.30.170.96:8181/rests/data/network-topology:network-topology/topology=topology-netconf/node=netconf-test-device?content=nonconfig
00:00:00.346 TEST Check_Device_Data_Is_Seen_As_Empty_On_Configurer
Full Name: netconf-clustering.txt.CRUD.Check_Device_Data_Is_Seen_As_Empty_On_Configurer
Documentation:

Get the device data as seen by configurer and make sure it is empty.
Start / End / Elapsed: 20250324 22:16:54.057 / 20250324 22:16:54.403 / 00:00:00.346
Status: PASS
00:00:10.611 TEST Check_Device_Data_Is_Seen_As_Empty_On_Checker
Full Name: netconf-clustering.txt.CRUD.Check_Device_Data_Is_Seen_As_Empty_On_Checker
Documentation:

Get the device data as seen by checker and make sure it is empty.
Start / End / Elapsed: 20250324 22:16:54.404 / 20250324 22:17:05.015 / 00:00:10.611
Status: FAIL
Message: Keyword 'Check_Config_Data' failed after retrying for 10 seconds. The last error was: HTTPError: 503 Server Error: Service Unavailable for url: http://10.30.171.154:8181/rests/data/network-topology:network-topology/topology=topology-netconf/node=netconf-test-device/yang-ext:mount?content=config
00:00:10.837 TEST Check_Device_Data_Is_Seen_As_Empty_On_Setter
Full Name: netconf-clustering.txt.CRUD.Check_Device_Data_Is_Seen_As_Empty_On_Setter
Documentation:

Get the device data as seen by setter and make sure it is empty.
Start / End / Elapsed: 20250324 22:17:05.016 / 20250324 22:17:15.853 / 00:00:10.837
Status: FAIL
Message: Keyword 'Check_Config_Data' failed after retrying for 10 seconds. The last error was: HTTPError: 503 Server Error: Service Unavailable for url: http://10.30.170.96:8181/rests/data/network-topology:network-topology/topology=topology-netconf/node=netconf-test-device/yang-ext:mount?content=config
00:00:00.422 TEST Create_Device_Data
Full Name: netconf-clustering.txt.CRUD.Create_Device_Data
Documentation:

Send some sample test data into the device and check that the request went OK.
Start / End / Elapsed: 20250324 22:17:15.853 / 20250324 22:17:16.275 / 00:00:00.422
Status: FAIL
Message: HTTPError: 503 Server Error: Service Unavailable for url: http://10.30.170.96:8181/rests/data/network-topology:network-topology/topology=topology-netconf/node=netconf-test-device/yang-ext:mount
00:00:10.583 TEST Check_New_Device_Data_Is_Visible_On_Setter
Full Name: netconf-clustering.txt.CRUD.Check_New_Device_Data_Is_Visible_On_Setter
Documentation:

Get the device data and make sure it contains the created content.
Start / End / Elapsed: 20250324 22:17:16.275 / 20250324 22:17:26.858 / 00:00:10.583
Status: FAIL
Message: Keyword 'Check_Config_Data' failed after retrying for 10 seconds. The last error was: HTTPError: 503 Server Error: Service Unavailable for url: http://10.30.170.96:8181/rests/data/network-topology:network-topology/topology=topology-netconf/node=netconf-test-device/yang-ext:mount?content=config
00:00:10.584 TEST Check_New_Device_Data_Is_Visible_On_Checker
Full Name: netconf-clustering.txt.CRUD.Check_New_Device_Data_Is_Visible_On_Checker
Documentation:

Check that the created device data make their way into the checker node.
Start / End / Elapsed: 20250324 22:17:26.858 / 20250324 22:17:37.442 / 00:00:10.584
Status: FAIL
Message: Keyword 'Check_Config_Data' failed after retrying for 10 seconds. The last error was: HTTPError: 503 Server Error: Service Unavailable for url: http://10.30.171.154:8181/rests/data/network-topology:network-topology/topology=topology-netconf/node=netconf-test-device/yang-ext:mount?content=config
00:00:10.960 TEST Check_New_Device_Data_Is_Visible_On_Configurer
Full Name: netconf-clustering.txt.CRUD.Check_New_Device_Data_Is_Visible_On_Configurer
Documentation:

Check that the created device data make their way into the configurer node.
Start / End / Elapsed: 20250324 22:17:37.442 / 20250324 22:17:48.402 / 00:00:10.960
Status: FAIL
Message: Keyword 'Check_Config_Data' failed after retrying for 10 seconds. The last error was: <data xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"></data> != <data xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"><cont xmlns="urn:opendaylight:test:netconf:crud"><l>Content</l></cont></data>
00:00:00.467 TEST Modify_Device_Data
Full Name: netconf-clustering.txt.CRUD.Modify_Device_Data
Documentation:

Send a request to change the sample test data and check that the request went OK.
Tags: https://bugs.opendaylight.org/show_bug.cgi?id=4968
Start / End / Elapsed: 20250324 22:17:48.402 / 20250324 22:17:48.869 / 00:00:00.467
Status: FAIL
Message: This test fails due to https://bugs.opendaylight.org/show_bug.cgi?id=4968 HTTPError: 503 Server Error: Service Unavailable for url: http://10.30.170.96:8181/rests/data/network-topology:network-topology/topology=topology-netconf/node=netconf-test-device/yang-ext:mount/test:cont
00:00:00.281 TEST Check_Device_Data_Is_Modified
Full Name: netconf-clustering.txt.CRUD.Check_Device_Data_Is_Modified
Documentation:

Get the device data and make sure it contains the modified content.
Tags: https://bugs.opendaylight.org/show_bug.cgi?id=4968
Start / End / Elapsed: 20250324 22:17:48.870 / 20250324 22:17:49.151 / 00:00:00.281
Status: FAIL
Message: This test fails due to https://bugs.opendaylight.org/show_bug.cgi?id=4968 HTTPError: 503 Server Error: Service Unavailable for url: http://10.30.170.96:8181/rests/data/network-topology:network-topology/topology=topology-netconf/node=netconf-test-device/yang-ext:mount?content=config
00:01:01.088 TEST Check_Modified_Device_Data_Is_Visible_On_Checker
Full Name: netconf-clustering.txt.CRUD.Check_Modified_Device_Data_Is_Visible_On_Checker
Documentation:

Check that the modified device data make their way into the checker node.
Tags: https://bugs.opendaylight.org/show_bug.cgi?id=4968
Start / End / Elapsed: 20250324 22:17:49.151 / 20250324 22:18:50.239 / 00:01:01.088
Status: FAIL
Message: This test fails due to https://bugs.opendaylight.org/show_bug.cgi?id=4968 Keyword 'Check_Config_Data' failed after retrying for 1 minute. The last error was: HTTPError: 503 Server Error: Service Unavailable for url: http://10.30.171.154:8181/rests/data/network-topology:network-topology/topology=topology-netconf/node=netconf-test-device/yang-ext:mount?content=config
00:01:00.937 TEST Check_Modified_Device_Data_Is_Visible_On_Configurer
Full Name: netconf-clustering.txt.CRUD.Check_Modified_Device_Data_Is_Visible_On_Configurer
Documentation:

Check that the modified device data make their way into the configurer node.
Tags: https://bugs.opendaylight.org/show_bug.cgi?id=4968
Start / End / Elapsed: 20250324 22:18:50.240 / 20250324 22:19:51.177 / 00:01:00.937
Status: FAIL
Message: This test fails due to https://bugs.opendaylight.org/show_bug.cgi?id=4968 Keyword 'Check_Config_Data' failed after retrying for 1 minute. The last error was: <data xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"></data> != <data xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"><cont xmlns="urn:opendaylight:test:netconf:crud"><l>Modified Content</l></cont></data>
00:00:00.332 TEST Delete_Device_Data
Full Name: netconf-clustering.txt.CRUD.Delete_Device_Data
Documentation:

Send a request to delete the sample test data on the device and check that the request went OK.
Tags: https://bugs.opendaylight.org/show_bug.cgi?id=4968
Start / End / Elapsed: 20250324 22:19:51.177 / 20250324 22:19:51.509 / 00:00:00.332
Status: FAIL
Message: This test fails due to https://bugs.opendaylight.org/show_bug.cgi?id=4968 HTTPError: 503 Server Error: Service Unavailable for url: http://10.30.170.96:8181/rests/data/network-topology:network-topology/topology=topology-netconf/node=netconf-test-device/yang-ext:mount/test:cont
00:00:00.258 TEST Check_Device_Data_Is_Deleted
Full Name: netconf-clustering.txt.CRUD.Check_Device_Data_Is_Deleted
Documentation:

Get the device data and make sure it is empty again.
Tags: https://bugs.opendaylight.org/show_bug.cgi?id=4968
Start / End / Elapsed: 20250324 22:19:51.510 / 20250324 22:19:51.768 / 00:00:00.258
Status: FAIL
Message: This test fails due to https://bugs.opendaylight.org/show_bug.cgi?id=4968 HTTPError: 503 Server Error: Service Unavailable for url: http://10.30.170.96:8181/rests/data/network-topology:network-topology/topology=topology-netconf/node=netconf-test-device/yang-ext:mount?content=config
00:01:01.027 TEST Check_Device_Data_Deletion_Is_Visible_On_Checker
Full Name: netconf-clustering.txt.CRUD.Check_Device_Data_Deletion_Is_Visible_On_Checker
Documentation:

Check that the device data deletion makes its way into the checker node.
Tags: https://bugs.opendaylight.org/show_bug.cgi?id=4968
Start / End / Elapsed: 20250324 22:19:51.767 / 20250324 22:20:52.794 / 00:01:01.027
Status: FAIL
Message: This test fails due to https://bugs.opendaylight.org/show_bug.cgi?id=4968 Keyword 'Check_Config_Data' failed after retrying for 1 minute. The last error was: HTTPError: 503 Server Error: Service Unavailable for url: http://10.30.171.154:8181/rests/data/network-topology:network-topology/topology=topology-netconf/node=netconf-test-device/yang-ext:mount?content=config
00:00:00.305 TEST Check_Device_Data_Deletion_Is_Visible_On_Configurer
Full Name: netconf-clustering.txt.CRUD.Check_Device_Data_Deletion_Is_Visible_On_Configurer
Documentation:

Check that the device data deletion makes its way into the checker node.
Start / End / Elapsed: 20250324 22:20:52.795 / 20250324 22:20:53.100 / 00:00:00.305
Status: PASS
00:00:00.369 TEST Deconfigure_Device_In_Netconf
Full Name: netconf-clustering.txt.CRUD.Deconfigure_Device_In_Netconf
Documentation:

Make request to deconfigure the device on Netconf connector.
Tags: critical
Start / End / Elapsed: 20250324 22:20:53.101 / 20250324 22:20:53.470 / 00:00:00.369
Status: PASS
00:00:00.294 TEST Check_Device_Deconfigured_On_Configurer
Full Name: netconf-clustering.txt.CRUD.Check_Device_Deconfigured_On_Configurer
Documentation:

Check that the device is really going to be gone. Fail if still there after one minute. This is an expected behavior as the unmount request is sent to the config subsystem which then triggers asynchronous disconnection of the device which is reflected in the operational data once completed. This test makes sure this asynchronous operation does not take unreasonable amount of time.
Tags: critical
Start / End / Elapsed: 20250324 22:20:53.471 / 20250324 22:20:53.765 / 00:00:00.294
Status: PASS
00:00:00.315 TEST Check_Device_Deconfigured_On_Checker
Full Name: netconf-clustering.txt.CRUD.Check_Device_Deconfigured_On_Checker
Documentation:

Check that the device is going to be gone from the checker node. Fail if still there after one minute.
Tags: critical
Start / End / Elapsed: 20250324 22:20:53.765 / 20250324 22:20:54.080 / 00:00:00.315
Status: PASS
00:00:00.319 TEST Check_Device_Deconfigured_On_Setter
Full Name: netconf-clustering.txt.CRUD.Check_Device_Deconfigured_On_Setter
Documentation:

Check that the device is going to be gone from the setter node. Fail if still there after one minute.
Tags: critical
Start / End / Elapsed: 20250324 22:20:54.080 / 20250324 22:20:54.399 / 00:00:00.319
Status: PASS
00:05:01.697 SUITE Bug8086
Full Name: netconf-clustering.txt.Bug8086
Documentation:

Simplified netconf clustered CRUD test suite in Bug 8086 setup.

Copyright (c) 2016 Cisco Systems, Inc. and others. All rights reserved.

This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html

Perform basic operations (Create, Read, Update and Delete or CRUD) on device data mounted onto a netconf connector and see if they work.

The suite recognizes 3 nodes, "CONFIGURER" (the node that configures the device at the beginning and then deconfigures it at the end), "SETTER" (the node that manipulates the data on the device) and "CHECKER" (the node that checks the data on the device). The configured device and the results of each data operation on it is expected to be visible on all nodes so after each operation three test cases make sure they can see the result on their respective nodes.

The 3 nodes are configured by placing "node1", "node2" or "node3" into the node1, node2 and node3 to make the node a "CONFIGURER", "SETTER" and "CHECKER" respectively. The "nodeX" name refers to the node with its IP address configured with the ${ODL_SYSTEM_X_IP} variable where the "X" is 1, 2 or 3.

The suite checks the integrity of the presence of the device and the data seen on the device only for nodes that have at least one of the roles ("CONFIGURER", "SETTER" and "CHECKER") assigned. A better design would have a "checker list" of sorts and have only one checking test case that runs through the check list and performs the test on each node listed. However this currently has fairly low priority due to Beryllium delivery date so it was left out.
Source: /w/workspace/netconf-csit-3node-clustering-only-scandium/test/csit/suites/netconf/clustering/bug8086.robot
Start / End / Elapsed: 20250324 22:20:54.793 / 20250324 22:25:56.490 / 00:05:01.697
Status: 26 tests total, 11 passed, 15 failed, 0 skipped
00:06:30.187 SUITE Restart Odl With Tell Based False
Full Name: netconf-clustering.txt.Restart Odl With Tell Based False
Documentation:

Unset tell-based protocol usage

Copyright (c) 2016 Cisco Systems, Inc. and others. All rights reserved.

This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html

Suite stops all odl nodes, outcomment usage of tell-based protocol in config file (means make it false by default) and starts all nodes again.
Source: /w/workspace/netconf-csit-3node-clustering-only-scandium/test/csit/suites/controller/dom_data_broker/restart_odl_with_tell_based_false.robot
Start / End / Elapsed: 20250324 22:25:56.492 / 20250324 22:32:26.679 / 00:06:30.187
Status: 3 tests total, 2 passed, 1 failed, 0 skipped
00:08:56.012 SUITE Entity
Full Name: netconf-clustering.txt.Entity
Documentation:

Test suite for netconf device entity ownership handling during outages.

Copyright (c) 2016 Cisco Systems, Inc. and others. All rights reserved.

This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html

Perform basic operations (Create, Read, Update and Delete or CRUD) on device data mounted onto a netconf connector and see if they work.

The suite recognizes 3 nodes, "CONFIGURER" (the node that configures the device at the beginning and then deconfigures it at the end), "SETTER" (the node that manipulates the data on the device) and "CHECKER" (the node that checks the data on the device). The configured device and the results of each data operation on it is expected to be visible on all nodes so after each operation three test cases make sure they can see the result on their respective nodes.

The 3 nodes are configured by placing "node1", "node2" or "node3" into the ${NODE_CONFIGURER}, ${NODE_SETTER} and ${NODE_CHECKER} to make the node a "CONFIGURER", "SETTER" and "CHECKER" respectively. The "nodeX" name refers to the node with its IP address configured with the ${ODL_SYSTEM_X_IP} variable where the "X" is 1, 2 or 3.

The suite checks the integrity of the presence of the device and the data seen on the device only for nodes that have at least one of the roles ("CONFIGURER", "SETTER" and "CHECKER") assigned. A better design would have a "checker list" of sorts and have only one checking test case that runs through the check list and performs the test on each node listed. However this currently has fairly low priority due to Beryllium delivery date so it was left out.
Source: /w/workspace/netconf-csit-3node-clustering-only-scandium/test/csit/suites/netconf/clustering/entity.robot
Start / End / Elapsed: 20250324 22:32:26.680 / 20250324 22:41:22.692 / 00:08:56.012
Status: 17 tests total, 2 passed, 15 failed, 0 skipped
00:06:33.129 SUITE Restart Odl With Tell Based False
Full Name: netconf-clustering.txt.Restart Odl With Tell Based False
Documentation:

Unset tell-based protocol usage

Copyright (c) 2016 Cisco Systems, Inc. and others. All rights reserved.

This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html

Suite stops all odl nodes, outcomment usage of tell-based protocol in config file (means make it false by default) and starts all nodes again.
Source: /w/workspace/netconf-csit-3node-clustering-only-scandium/test/csit/suites/controller/dom_data_broker/restart_odl_with_tell_based_false.robot
Start / End / Elapsed: 20250324 22:41:22.693 / 20250324 22:47:55.822 / 00:06:33.129
Status: 3 tests total, 2 passed, 1 failed, 0 skipped
00:17:31.703 SUITE Outages
Full Name: netconf-clustering.txt.Outages
Documentation:

netconf cluster node outage test suite (CRUD operations).

Copyright (c) 2016 Cisco Systems, Inc. and others. All rights reserved.

This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html

Perform one of the basic operations (Create, Read, Update and Delete or CRUD) on device data mounted onto a netconf connector while one of the nodes is down and see if they work. Then bring the dead node up and check that it sees the operations that were made while it was down are visible on it as well.

The node is brought down before each of the "Create", "Update" and "Delete" operations and brought and back up after these operations. Before the dead node is brought up, a test case makes sure the operation is properly propagated within the cluster.

Currently each of the 3 operations is done once. "Create" is done while node 1 is down, "Update" while node 2 is down and "Delete" while node 3 is down.
Source: /w/workspace/netconf-csit-3node-clustering-only-scandium/test/csit/suites/netconf/clustering/outages.robot
Start / End / Elapsed: 20250324 22:47:55.823 / 20250324 23:05:27.526 / 00:17:31.703
Status: 22 tests total, 8 passed, 14 failed, 0 skipped
00:08:54.582 SUITE Entity
Full Name: netconf-clustering.txt.Entity
Documentation:

Test suite for netconf device entity ownership handling during outages.

Copyright (c) 2016 Cisco Systems, Inc. and others. All rights reserved.

This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html

Perform basic operations (Create, Read, Update and Delete or CRUD) on device data mounted onto a netconf connector and see if they work.

The suite recognizes 3 nodes, "CONFIGURER" (the node that configures the device at the beginning and then deconfigures it at the end), "SETTER" (the node that manipulates the data on the device) and "CHECKER" (the node that checks the data on the device). The configured device and the results of each data operation on it is expected to be visible on all nodes so after each operation three test cases make sure they can see the result on their respective nodes.

The 3 nodes are configured by placing "node1", "node2" or "node3" into the ${NODE_CONFIGURER}, ${NODE_SETTER} and ${NODE_CHECKER} to make the node a "CONFIGURER", "SETTER" and "CHECKER" respectively. The "nodeX" name refers to the node with its IP address configured with the ${ODL_SYSTEM_X_IP} variable where the "X" is 1, 2 or 3.

The suite checks the integrity of the presence of the device and the data seen on the device only for nodes that have at least one of the roles ("CONFIGURER", "SETTER" and "CHECKER") assigned. A better design would have a "checker list" of sorts and have only one checking test case that runs through the check list and performs the test on each node listed. However this currently has fairly low priority due to Beryllium delivery date so it was left out.
Source: /w/workspace/netconf-csit-3node-clustering-only-scandium/test/csit/suites/netconf/clustering/entity.robot
Start / End / Elapsed: 20250324 23:05:27.528 / 20250324 23:14:22.110 / 00:08:54.582
Status: 17 tests total, 2 passed, 15 failed, 0 skipped
00:05:11.323 SUITE CRUD
Full Name: netconf-clustering.txt.CRUD
Documentation:

netconf clustered CRUD test suite.

Copyright (c) 2016 Cisco Systems, Inc. and others. All rights reserved.

This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html

Perform basic operations (Create, Read, Update and Delete or CRUD) on device data mounted onto a netconf connector and see if they work.

The suite recognizes 3 nodes, "CONFIGURER" (the node that configures the device at the beginning and then deconfigures it at the end), "SETTER" (the node that manipulates the data on the device) and "CHECKER" (the node that checks the data on the device). The configured device and the results of each data operation on it is expected to be visible on all nodes so after each operation three test cases make sure they can see the result on their respective nodes.

The 3 nodes are configured by placing "node1", "node2" or "node3" into the node1, node2 and node3 to make the node a "CONFIGURER", "SETTER" and "CHECKER" respectively. The "nodeX" name refers to the node with its IP address configured with the ${ODL_SYSTEM_X_IP} variable where the "X" is 1, 2 or 3.

The suite checks the integrity of the presence of the device and the data seen on the device only for nodes that have at least one of the roles ("CONFIGURER", "SETTER" and "CHECKER") assigned. A better design would have a "checker list" of sorts and have only one checking test case that runs through the check list and performs the test on each node listed. However this currently has fairly low priority due to Beryllium delivery date so it was left out.
Source: /w/workspace/netconf-csit-3node-clustering-only-scandium/test/csit/suites/netconf/clustering/CRUD.robot
Start / End / Elapsed: 20250324 23:14:22.111 / 20250324 23:19:33.434 / 00:05:11.323
Status: 26 tests total, 10 passed, 16 failed, 0 skipped