Fix instance boot when metadata exists 63/49863/1
authortomsou <soth@intracom-telecom.com>
Tue, 24 Oct 2017 14:37:37 +0000 (17:37 +0300)
committerThomas Sounapoglou <soth@intracom-telecom.com>
Tue, 2 Jan 2018 15:34:58 +0000 (15:34 +0000)
commitd81779daee14b1567f4f4a0a55509c8ba35909d4
tree17a55dc8b69d2df83e44ad89f52a774a16fcc5f3
parent43ab8814f2ac3e39d7aa96ca2ca23a63fb6d1a27
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>
(cherry picked from commit a6e207c16430055eba8bcc8586b09a7081db3d04)
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