[MANOPD-68698] Fix check_iaas procedure when cluster is not installed

[ilia1243]

Description

1. When cluster is not installed, check_iaas might fail, but succeed after cluster installation.
2. When cluster is installed, check_iaas does not fail, but tries to connect to services listening predefined ports (for example, 80, 6443)

Solution

• socat utility might be not installed before cluster installation. Simple custom tcp listener that can be run on python 2 or 3 is used instead of socat.
• If firewalld service is enabled in any node, temporarily stop the service. The fact that it should be disabled, is checked by check_paas procedure by services.security.firewalld.status task.
• check_iaas now checks that ports and subnet can be already in use on some nodes. Such nodes are skipped from connectivity check with warnings.

Test Cases

TestCase 1

Test Configuration:

• Hardware: clean VMs with not install socat package on nodes, or with enabled firewalld service.

Steps:

1. Run check_iaas.

Results:

Before	After
network tasks fail	network tasks succeed

TestCase 2

Test Configuration:

• Any installed cluster

Steps:

1. Run check_iaas.

Results:

Before	After
network.check_tcp_ports does not fail	network.check_tcp_ports is skipped with warnings, because some ports are in use

Checklist

• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• Integration CI passed
• Unit tests. If Yes list of new/changed tests with brief description
• There is no merge conflicts

Reviewers

@koryaga @iLeonidze @Zaborin @alexarefev @Yaroslav-Lahtachev @dmyar21

[andrewluckyguy]

Tested by QA for Centos and Ubuntu:

• on clean VMs
• on deployed cluster