tree caa824a33d9ac54fc4cef5a4ccabf5f328120b87
parent 6f1f2a4efce87bd525100631f29d6b22a7e3a727
author George Keishing <gkeishin@in.ibm.com> 1617262302 -0500
committer George Keishing <gkeishin@in.ibm.com> 1617288182 +0000

Handle RobotNotRunningError in FFDC script

We noticed that in our env, we see throwing out exception but
doesnt impact the over all flow. FFDC should irrespective of
failure should continue and collect log as much possible.

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