Fix "netconf_is_ready" not always reflecting netconf status 64/33564/2
authorJozef Behran <jbehran@cisco.com>
Tue, 26 Jan 2016 15:38:26 +0000 (16:38 +0100)
committerGerrit Code Review <gerrit@opendaylight.org>
Wed, 27 Jan 2016 10:42:01 +0000 (10:42 +0000)
commit548fd35158bca7bc81ae8b8a51f4b727f0eba552
tree726b26ed355c1f45ac02368776759151d74326ef
parent17e802a3ed58bb640da1346fd639709803d6b49d
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>
csit/suites/netconf/ready/netconfready.robot