Total Statistics | Total | Pass | Fail | Skip | Elapsed | Pass / Fail / Skip |
---|---|---|---|---|---|---|
All Tests | 1 | 0 | 1 | 0 | 00:00:01 |
Statistics by Tag | Total | Pass | Fail | Skip | Elapsed | Pass / Fail / Skip |
---|---|---|---|---|---|---|
critical | 1 | 0 | 1 | 0 | 00:00:01 |
Statistics by Suite | Total | Pass | Fail | Skip | Elapsed | Pass / Fail / Skip |
---|---|---|---|---|---|---|
1 | 0 | 1 | 0 | 00:00:06 |
Full Name: | controller-drb-precedence-longevity.txt |
---|---|
Documentation: | DOMRpcBroker testing: RPC Provider Precedence Copyright (c) 2017 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 The aim is to establish that remote RPC implementations have lower priority than local ones, which is to say that any movement of RPCs on remote nodes does not affect routing as long as a local implementation is available. |
Source: | /w/workspace/controller-csit-3node-drb-precedence-longevity-only-calcium/test/csit/suites/controller/dom_rpc_broker/rpc_provider_precedence_longevity.robot |
Start / End / Elapsed: | 20250301 23:28:42.646 / 20250301 23:28:48.727 / 00:00:06.081 |
Status: | 1 test total, 0 passed, 1 failed, 0 skipped |
Documentation: | Create a list of possible constant responses on the node with unregistered rpc. |
---|---|
Start / End / Elapsed: | 20250301 23:28:43.179 / 20250301 23:28:48.154 / 00:00:04.975 |
Documentation: | Closes all open connections. |
---|---|
Start / End / Elapsed: | 20250301 23:28:48.727 / 20250301 23:28:48.727 / 00:00:00.000 |
Full Name: | controller-drb-precedence-longevity.txt.Rpc_Provider_Precedence_Longevity |
---|---|
Documentation: | Repeat the tested scenario for 24h. |
Tags: | critical |
Start / End / Elapsed: | 20250301 23:28:48.154 / 20250301 23:28:48.726 / 00:00:00.572 |
Status: | FAIL |
Message: |
Documentation: | Test case setup which explicitly ignores previous failure and logs test case name to Karaf log. Needed if the recommended default is to be overriden. |
---|---|
Start / End / Elapsed: | 20250301 23:28:48.155 / 20250301 23:28:48.493 / 00:00:00.338 |
Documentation: | Register global rpc on given nodes of the cluster. |
---|---|
Start / End / Elapsed: | 20250301 23:28:48.494 / 20250301 23:28:48.715 / 00:00:00.221 |
Start / End / Elapsed: | 20250301 23:28:48.494 / 20250301 23:28:48.714 / 00:00:00.220 |
---|
Start / End / Elapsed: | 20250301 23:28:48.494 / 20250301 23:28:48.714 / 00:00:00.220 |
---|
Documentation: | Register global rpc on given node of the cluster. |
---|---|
Start / End / Elapsed: | 20250301 23:28:48.494 / 20250301 23:28:48.714 / 00:00:00.220 |
Documentation: | Register the get-constant rpc on the requested node with given constant. |
---|---|
Start / End / Elapsed: | 20250301 23:28:48.494 / 20250301 23:28:48.713 / 00:00:00.219 |
Documentation: | Return RequestsLibrary session alias pointing to node of given index. |
---|---|
Start / End / Elapsed: | 20250301 23:28:48.495 / 20250301 23:28:48.496 / 00:00:00.001 |
Documentation: | Creates and returns a dictionary based on the given |
---|---|
Start / End / Elapsed: | 20250301 23:28:48.496 / 20250301 23:28:48.496 / 00:00:00.000 |
Documentation: | Add arguments sensible for XML data, return Post_Templated response text. Optionally, verification against response.xml (no iteration) is called. |
---|---|
Start / End / Elapsed: | 20250301 23:28:48.496 / 20250301 23:28:48.713 / 00:00:00.217 |
Documentation: | Resolve URI and data from folder, call Post_To_Uri, return response text. |
---|---|
Start / End / Elapsed: | 20250301 23:28:48.500 / 20250301 23:28:48.712 / 00:00:00.212 |
Documentation: | Read a template from folder, strip endline, make changes according to mapping, return the result. If ${iterations} value is present, put text together from "prolog", "item" and "epilog" parts, where additional template variable ${i} goes from 1, by one times. Template variable ${j} is calculated as ${i} incremented by offset 0 ( j = i + iter_j_offset ) used to create non uniform data in order to be able to validate UPDATE operations. POST (as opposed to PUT) needs slightly different data, ${name_prefix} may be used to distinguish. (Actually, it is GET who formats data differently when URI is a top-level container.) |
---|---|
Start / End / Elapsed: | 20250301 23:28:48.510 / 20250301 23:28:48.571 / 00:00:00.061 |
Documentation: | Read a template from folder, strip endline, make changes according to mapping, return the result. If ${iterations} value is present, put text together from "prolog", "item" and "epilog" parts, where additional template variable ${i} goes from 1, by one times. Template variable ${j} is calculated as ${i} incremented by offset 0 ( j = i + iter_j_offset ) used to create non uniform data in order to be able to validate UPDATE operations. POST (as opposed to PUT) needs slightly different data, ${name_prefix} may be used to distinguish. (Actually, it is GET who formats data differently when URI is a top-level container.) |
---|---|
Start / End / Elapsed: | 20250301 23:28:48.581 / 20250301 23:28:48.636 / 00:00:00.055 |
Documentation: | Reads JMES path from file /w/workspace/controller-csit-3node-drb-precedence-longevity-only-calcium/test/csit/libraries/../variables/mdsal/lowlevelrpc/register_constant/jmespath.expr if the file exists and returns the JMES path. Empty string is returned otherwise. |
---|---|
Start / End / Elapsed: | 20250301 23:28:48.636 / 20250301 23:28:48.640 / 00:00:00.004 |
Documentation: | POST data to given URI, check status code and return response text. ${content_type} and ${accept} are mandatory Python objects with headers to use. If ${normalize_json}, normalize text before returning. |
---|---|
Start / End / Elapsed: | 20250301 23:28:48.641 / 20250301 23:28:48.712 / 00:00:00.071 |
Documentation: | Logs the given message with the given level. |
---|---|
Start / End / Elapsed: | 20250301 23:28:48.641 / 20250301 23:28:48.641 / 00:00:00.000 |
Documentation: | Logs the given message with the given level. |
---|---|
Start / End / Elapsed: | 20250301 23:28:48.642 / 20250301 23:28:48.642 / 00:00:00.000 |
Documentation: | Logs the given message with the given level. |
---|---|
Start / End / Elapsed: | 20250301 23:28:48.642 / 20250301 23:28:48.642 / 00:00:00.000 |
Documentation: | Logs the given message with the given level. |
---|---|
Start / End / Elapsed: | 20250301 23:28:48.642 / 20250301 23:28:48.642 / 00:00:00.000 |
Documentation: | Take two dicts, join them, return result. Second argument values take precedence. |
---|---|
Start / End / Elapsed: | 20250301 23:28:48.643 / 20250301 23:28:48.645 / 00:00:00.002 |
Start / End / Elapsed: | 20250301 23:28:48.645 / 20250301 23:28:48.711 / 00:00:00.066 |
---|
Start / End / Elapsed: | 20250301 23:28:48.710 / 20250301 23:28:48.710 / 00:00:00.000 |
---|
Documentation: | Log response text, check status_code is one of allowed ones. In cases where this keyword is called in a WUKS it could end up logging tons of data and it may be desired to skip the logging by passing log_response=False, but by default it remains True. |
---|---|
Start / End / Elapsed: | 20250301 23:28:48.711 / 20250301 23:28:48.711 / 00:00:00.000 |
Start / End / Elapsed: | 20250301 23:28:48.711 / 20250301 23:28:48.711 / 00:00:00.000 |
---|
Documentation: | Attempt to return sorted indented JSON string. |
---|---|
Start / End / Elapsed: | 20250301 23:28:48.712 / 20250301 23:28:48.712 / 00:00:00.000 |
Start / End / Elapsed: | 20250301 23:28:48.712 / 20250301 23:28:48.712 / 00:00:00.000 |
---|
Documentation: | Add a constant to the [] list. The list is about to maintain all valid constants possibly responded from the odl cluster (excluding isolated nodes). |
---|---|
Start / End / Elapsed: | 20250301 23:28:48.713 / 20250301 23:28:48.713 / 00:00:00.000 |
Documentation: | Some positive checks report false success for a short time. This keyword verifies no failure does happen within timeout period. This implementation needs more complicated logic than, Verify_Keyword_Never_Passes_Within_Timeout, so use that keyword in case you have a negative check handy. |
---|---|
Start / End / Elapsed: | 20250301 23:28:48.714 / 20250301 23:28:48.714 / 00:00:00.000 |
Documentation: | Unregister global rpc on given nodes of the cluster. |
---|---|
Start / End / Elapsed: | 20250301 23:28:48.715 / 20250301 23:28:48.715 / 00:00:00.000 |