Fix "netconf_is_ready" not always reflecting netconf status

If the "Check_Whether_Netconf_Is_Up_And_Running" test case
fails or is skipped, the "netconf_is_ready" is left set to
False even when "Wait_For_Netconf" concludes that Netconf IS
ready. This will break further test cases if they rely on
"netconf_is_ready" to determine whether the Netconf was seen
to be up and running or not. The fix simply tells the
"Wait_For_Netconf" test case to update the variable.

Change-Id: I05e18cd491dc414b036cb68504dcf3b39e0c2490
Signed-off-by: Jozef Behran <jbehran@cisco.com>

diff --git a/csit/suites/netconf/ready/netconfready.robot b/csit/suites/netconf/ready/netconfready.robot
index 125e9c275a6f1381c642c4fffa36001c72ba202b..ec0ecb57c900e5d25771773c58144238759ddec5 100644 (file)
--- a/csit/suites/netconf/ready/netconfready.robot
+++ b/csit/suites/netconf/ready/netconfready.robot
@@ -46,6 +46,7 @@ Wait_For_Netconf_Connector
     [Documentation]    Attempt to wait for the netconf-connector for configurable time.
     [Tags]    critical
     BuiltIn.Run_Keyword_Unless    ${netconf_is_ready}    BuiltIn.Wait_Until_Keyword_Succeeds    ${NETCONFREADY_WAIT}    1s    Check_Netconf_Connector
+    BuiltIn.Set_Suite_Variable    ${netconf_is_ready}    True
     [Teardown]    Utils.Report_Failure_Due_To_Bug    4583
 
 Check_Whether_Netconf_Connector_Can_Pretty_Print