4.3.0 manager bootstrap sanity problems with port 8080 in use

Description

If port 8080 is in use on a VM where 4.3.0 is being bootstrapped, the sanity check will repeatedly fail trying to uninstall- this is likely because the process that it is trying to kill exits when it tries to bind to that port.

This can be reproduced by trying to perform an in-place upgrade from, e.g. 4.2 where a hello world or nodecellar blueprint was installed on the manager, using port 8080.
Tearing down without uninstalling the blueprint and then trying to install 4.3.0 will result in the sanity retrying the uninstall repeatedly.

Assignee

Unassigned

Reporter

geokala

Labels

Bug Type

legacy bug

Target Version

4.3

Severity

High

Sprint

None

Fix versions

Affects versions

Configure