Total Statistics | Total | Pass | Fail | Skip | Elapsed | Pass / Fail / Skip |
---|---|---|---|---|---|---|
All Tests | 140 | 116 | 24 | 0 | 00:24:02 |
Statistics by Tag | Total | Pass | Fail | Skip | Elapsed | Pass / Fail / Skip |
---|---|---|---|---|---|---|
critical | 40 | 32 | 8 | 0 | 00:13:45 | |
| 2 | 0 | 2 | 0 | 00:00:01 | |
| 6 | 0 | 6 | 0 | 00:05:25 | |
| 4 | 0 | 4 | 0 | 00:02:53 | |
| 4 | 0 | 4 | 0 | 00:04:04 |
Statistics by Suite | Total | Pass | Fail | Skip | Elapsed | Pass / Fail / Skip |
---|---|---|---|---|---|---|
140 | 116 | 24 | 0 | 00:24:43 | ||
26 | 26 | 0 | 0 | 00:00:29 | ||
26 | 26 | 0 | 0 | 00:00:22 | ||
3 | 3 | 0 | 0 | 00:01:31 | ||
17 | 8 | 9 | 0 | 00:06:22 | ||
3 | 3 | 0 | 0 | 00:01:27 | ||
22 | 16 | 6 | 0 | 00:07:56 | ||
17 | 8 | 9 | 0 | 00:06:18 | ||
26 | 26 | 0 | 0 | 00:00:18 |
Full Name: | netconf-clustering.txt |
---|---|
Start / End / Elapsed: | 20240804 02:54:17.143 / 20240804 03:19:00.621 / 00:24:43.478 |
Status: | 140 tests total, 116 passed, 24 failed, 0 skipped |
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-potassium/test/csit/suites/netconf/clustering/CRUD.robot |
Start / End / Elapsed: | 20240804 02:54:17.166 / 20240804 02:54:46.093 / 00:00:28.927 |
Status: | 26 tests total, 26 passed, 0 failed, 0 skipped |
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-potassium/test/csit/suites/netconf/clustering/bug8086.robot |
Start / End / Elapsed: | 20240804 02:54:46.094 / 20240804 02:55:08.001 / 00:00:21.907 |
Status: | 26 tests total, 26 passed, 0 failed, 0 skipped |
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-potassium/test/csit/suites/controller/dom_data_broker/restart_odl_with_tell_based_false.robot |
Start / End / Elapsed: | 20240804 02:55:08.003 / 20240804 02:56:39.237 / 00:01:31.234 |
Status: | 3 tests total, 3 passed, 0 failed, 0 skipped |
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-potassium/test/csit/suites/netconf/clustering/entity.robot |
Start / End / Elapsed: | 20240804 02:56:39.238 / 20240804 03:03:00.916 / 00:06:21.678 |
Status: | 17 tests total, 8 passed, 9 failed, 0 skipped |
Documentation: | Setup everything needed for the test cases. |
---|---|
Start / End / Elapsed: | 20240804 02:56:39.338 / 20240804 02:56:45.170 / 00:00:05.832 |
Documentation: | Teardown the test infrastructure, perform cleanup and release all resources. |
---|---|
Start / End / Elapsed: | 20240804 03:03:00.525 / 20240804 03:03:00.916 / 00:00:00.391 |
Full Name: | netconf-clustering.txt.Entity.Start_Testtool |
---|---|
Documentation: | Deploy and start test tool, then wait for all its devices to become online. |
Start / End / Elapsed: | 20240804 02:56:45.170 / 20240804 02:56:48.598 / 00:00:03.428 |
Status: | PASS |
Full Name: | netconf-clustering.txt.Entity.Check_Device_Is_Not_Mounted_At_Beginning |
---|---|
Documentation: | Sanity check making sure our device is not there. Fail if found. |
Start / End / Elapsed: | 20240804 02:56:48.598 / 20240804 02:56:49.153 / 00:00:00.555 |
Status: | PASS |
Full Name: | netconf-clustering.txt.Entity.Configure_Device_On_Netconf |
---|---|
Documentation: | Use node 1 to configure a testtool device on Netconf connector. |
Start / End / Elapsed: | 20240804 02:56:49.153 / 20240804 02:56:49.698 / 00:00:00.545 |
Status: | PASS |
Full Name: | netconf-clustering.txt.Entity.Wait_For_Device_To_Become_Visible_For_All_Nodes |
---|---|
Documentation: | Wait for the whole cluster to see the device. |
Start / End / Elapsed: | 20240804 02:56:49.699 / 20240804 02:56:52.462 / 00:00:02.763 |
Status: | PASS |
Full Name: | netconf-clustering.txt.Entity.Check_Config_Data_Before_Data_Creation |
---|---|
Documentation: | Check if there really is no data present on none of the nodes |
Start / End / Elapsed: | 20240804 02:56:52.462 / 20240804 02:56:53.097 / 00:00:00.635 |
Status: | PASS |
Full Name: | netconf-clustering.txt.Entity.Create_Device_Data |
---|---|
Documentation: | Create some data on the device and propagate it throughout the cluster. |
Start / End / Elapsed: | 20240804 02:56:53.097 / 20240804 02:56:53.682 / 00:00:00.585 |
Status: | PASS |
Full Name: | netconf-clustering.txt.Entity.Check_Config_Data_After_Data_Creation |
---|---|
Documentation: | Check if the data we just added into the cluster is really there |
Start / End / Elapsed: | 20240804 02:56:53.682 / 20240804 02:56:54.148 / 00:00:00.466 |
Status: | PASS |
Full Name: | netconf-clustering.txt.Entity.Find_And_Shutdown_Device_Entity_Owner |
---|---|
Documentation: | Simulate a failure of the owner of the entity that represents the device. |
Start / End / Elapsed: | 20240804 02:56:54.149 / 20240804 02:56:54.540 / 00:00:00.391 |
Status: | FAIL |
Message: |
Full Name: | netconf-clustering.txt.Entity.Wait_For_New_Owner_To_Appear |
---|---|
Documentation: | Wait for the cluster to recover from the failure and choose a new owner for the entity. |
Tags: | critical |
Start / End / Elapsed: | 20240804 02:56:54.539 / 20240804 02:58:55.352 / 00:02:00.813 |
Status: | FAIL |
Message: |
Full Name: | netconf-clustering.txt.Entity.Check_Config_Data_Before_Modification_With_Original_Owner_Down |
---|---|
Documentation: | Check if data is present and retrievable from follower nodes |
Tags: | https://bugs.opendaylight.org/show_bug.cgi?id=6067 |
Start / End / Elapsed: | 20240804 02:58:55.353 / 20240804 02:59:56.284 / 00:01:00.931 |
Status: | FAIL |
Message: |
Full Name: | netconf-clustering.txt.Entity.Modify_Device_Data_When_Original_Owner_Is_Down |
---|---|
Documentation: | Attempt to modify the data on the device after recovery and see if it still works. |
Tags: | https://bugs.opendaylight.org/show_bug.cgi?id=4968 |
Start / End / Elapsed: | 20240804 02:59:56.284 / 20240804 02:59:56.559 / 00:00:00.275 |
Status: | FAIL |
Message: |
Full Name: | netconf-clustering.txt.Entity.Check_Config_Data_After_Modification_With_Original_Owner_Down |
---|---|
Documentation: | Check if data is written correctly when original owner is shut down |
Tags: | https://bugs.opendaylight.org/show_bug.cgi?id=6067 |
Start / End / Elapsed: | 20240804 02:59:56.559 / 20240804 03:00:57.479 / 00:01:00.920 |
Status: | FAIL |
Message: |
Full Name: | netconf-clustering.txt.Entity.Restart_Original_Entity_Owner |
---|---|
Documentation: | Restart the original entity owner and see if it can still see the device and the new data on it. |
Start / End / Elapsed: | 20240804 03:00:57.480 / 20240804 03:00:57.765 / 00:00:00.285 |
Status: | FAIL |
Message: |
Full Name: | netconf-clustering.txt.Entity.Check_Config_Data_After_Original_Owner_Restart |
---|---|
Documentation: | Sanity check if we still can retrieve our data from the original device owner. |
Tags: | https://bugs.opendaylight.org/show_bug.cgi?id=5761 |
Start / End / Elapsed: | 20240804 03:00:57.764 / 20240804 03:01:58.620 / 00:01:00.856 |
Status: | FAIL |
Message: |
Full Name: | netconf-clustering.txt.Entity.Modify_Device_Data_With_Original_Owner |
---|---|
Documentation: | Check that the original owner of the entity is still able to modify the data on the device |
Tags: | https://bugs.opendaylight.org/show_bug.cgi?id=5761 |
Start / End / Elapsed: | 20240804 03:01:58.621 / 20240804 03:01:58.887 / 00:00:00.266 |
Status: | FAIL |
Message: |
Full Name: | netconf-clustering.txt.Entity.Check_Config_Data_After_Modification_With_Original_Owner_Up |
---|---|
Documentation: | Check if data has really been written as we expect. Fails if Modify_Device_Data_With_Original_Owner fails. |
Start / End / Elapsed: | 20240804 03:01:58.887 / 20240804 03:02:59.817 / 00:01:00.930 |
Status: | FAIL |
Message: |
Full Name: | netconf-clustering.txt.Entity.Deconfigure_Device_In_Netconf |
---|---|
Documentation: | Make request to deconfigure the device on Netconf connector and see if it works. |
Tags: | critical |
Start / End / Elapsed: | 20240804 03:02:59.818 / 20240804 03:03:00.525 / 00:00:00.707 |
Status: | PASS |
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-potassium/test/csit/suites/controller/dom_data_broker/restart_odl_with_tell_based_false.robot |
Start / End / Elapsed: | 20240804 03:03:00.917 / 20240804 03:04:27.652 / 00:01:26.735 |
Status: | 3 tests total, 3 passed, 0 failed, 0 skipped |
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-potassium/test/csit/suites/netconf/clustering/outages.robot |
Start / End / Elapsed: | 20240804 03:04:27.652 / 20240804 03:12:23.928 / 00:07:56.276 |
Status: | 22 tests total, 16 passed, 6 failed, 0 skipped |
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-potassium/test/csit/suites/netconf/clustering/entity.robot |
Start / End / Elapsed: | 20240804 03:12:23.929 / 20240804 03:18:42.270 / 00:06:18.341 |
Status: | 17 tests total, 8 passed, 9 failed, 0 skipped |
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-potassium/test/csit/suites/netconf/clustering/CRUD.robot |
Start / End / Elapsed: | 20240804 03:18:42.271 / 20240804 03:19:00.620 / 00:00:18.349 |
Status: | 26 tests total, 26 passed, 0 failed, 0 skipped |