Verify restconf is available on member startup
CSIT run
https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/controller-csit-3node-clustering-tell-all-neon/106/robot-plugin/log.html.gz
failed due to the restconf availability check returning 404.
This occurred at 17:16:24 however the karaf log shows that
the restconf bundle was still in the process of starting up
at that time (it was waiting for ia AAA dependency). The
bundle eventually completed startup at 17:17:19.
The restconf check is part of the
Get_Raft_Property_From_Shard_Member keyword. However it's
wrapped in the higher-level
Verify_Leader_Exists_For_Each_Shard keyword with a deadline
of 30 sec which is enough most of the time but needs a bigger
cushion. Unfortunately, since the restconf check is deeply
nested within a Wait Until Keyword Succeeds, we can't just
simply wrap it with it's own deadline as that may be longer
than the enclosing deadline. Instead, I added the restconf
check to the Start_Members_From_List_Or_All keyword which
already has a 5 min deadline. I left
Get_Raft_Property_From_Shard_Member as is lthough I really
don't think the restconf check belongs there.
Change-Id: I687a10cbc92d8190a2bcb9a5f4ac1837ba0459a8
Signed-off-by: Tom Pantelis <tompantelis@gmail.com>
Signed-off-by: Jamo Luhrsen <jluhrsen@redhat.com>