Added additional response checking to the onosStart() function
when onos-service <node ip> start is called,
sometimes the command returns no response but still starts the
ONOS service, this change addresses that case
Change-Id: Ie0fdb1b52043506fa2cf2274cffd598af2a2f6ac
diff --git a/TestON/drivers/common/cli/onosdriver.py b/TestON/drivers/common/cli/onosdriver.py
index 7df5a6c..32856b4 100644
--- a/TestON/drivers/common/cli/onosdriver.py
+++ b/TestON/drivers/common/cli/onosdriver.py
@@ -991,6 +991,7 @@
i = self.handle.expect( [
"Job\sis\salready\srunning",
"start/running",
+ "\$",
"Unknown\sinstance",
pexpect.TIMEOUT ], timeout=120 )
self.handle.expect( "\$" )
@@ -1000,6 +1001,9 @@
elif i == 1:
main.log.info( "ONOS service started" )
return main.TRUE
+ elif i == 2:
+ main.log.info( "ONOS service started" )
+ return main.TRUE
else:
main.log.error( "ONOS service failed to start" )
main.cleanup()