Bug fix: vping_userdata test status was not properly reported 19/43919/1
authorMorgan Richomme <morgan.richomme@orange.com>
Mon, 2 Oct 2017 15:11:13 +0000 (17:11 +0200)
committerMorgan Richomme <morgan.richomme@orange.com>
Mon, 2 Oct 2017 16:18:53 +0000 (16:18 +0000)
commitb7f390c91994cbcebac60e55f32a543cd4d46c1c
tree378e8aeaf1e3fdc834e0790e23aba4fa61beb329
parentaf96104859b803ac52ae096b2529a67b0f1725af
Bug fix: vping_userdata test status was not properly reported

vping_base is calling vping_userdata
vping_user data could return only EX_TESTCASE_FAILED or EX_OK
by default vping_base always returns EX_OK (based on self.result=100..)
it returned EX_RUN_ERROR only if upper class report EX_RUN_ERROR

that is why vping_userdata was always PASS even if the trace "Ping OK"
cannot be retrieved from the Nova console

it seems that when running the vping_userdata, we systematically got
 Failed to read iid from metadata

Change-Id: If72441dd93bffada5c7a5399c87db68d7ebeebed
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
(cherry picked from commit e36a14f6db0bc5ac93469bb553810de506f29bef)
functest/opnfv_tests/openstack/vping/vping_base.py