Fix instance boot when metadata exists 69/46169/2
authortomsou <soth@intracom-telecom.com>
Tue, 24 Oct 2017 14:37:37 +0000 (17:37 +0300)
committertomsou <soth@intracom-telecom.com>
Mon, 6 Nov 2017 11:10:38 +0000 (13:10 +0200)
commita6e207c16430055eba8bcc8586b09a7081db3d04
treea9d7c527e7292d714f5bca534d6d203ba4ad461e
parent4245d81de9226f64321dcd828e2a91ac912cf7d7
Fix instance boot when metadata exists

The way that a instance is considered as UP is pretty
strict and returns ERROR in case of instances with userdata

This patch differentiates the instances that are supposed to
boot till login prompt and those with userdata parameter

JIRA: SDNVPN-177

Change-Id: Ic4755366df006669475c90cc0693ac802256f379
Signed-off-by: tomsou <soth@intracom-telecom.com>
sdnvpn/lib/utils.py
sdnvpn/test/functest/testcase_1.py
sdnvpn/test/functest/testcase_10.py
sdnvpn/test/functest/testcase_2.py
sdnvpn/test/functest/testcase_4.py
sdnvpn/test/functest/testcase_7.py
sdnvpn/test/functest/testcase_8.py