tree 6754b626bd99f259db7c52c4ba313907bb2a5dc8
parent 7423c01a4633959b6132d38ef1f537be36def3a3
author George Keishing <gkeishin@in.ibm.com> 1476264568 -0500
committer Andrew Geissler <geissonator@yahoo.com> 1476481344 +0000

SOL utility process running check

Robot 'Start Command' keyword starts execution of the command
on the remote machine and returns immediately. This keyword
returns nothing and does not wait for the command execution
to be finished.

So if SOL starting failed we are not catching this error.
This had to be mitigated when stopping the SOL to verify if
the process is running or not. if not it will log and return
'No obmc-console-client process running' string back to the
caller.

This fix is to avoid other user of this utility not to fail
just because it failed to start, but allows the user to have
it own failing mechanism based out of the return output.

Resolves openbmc/openbmc-test-automation#152

Change-Id: I5c602fc5cf4257e0fe17ad347c264e75ccd6282d
Signed-off-by: George Keishing <gkeishin@in.ibm.com>