CI: Allow restart of the container if it fails on the first attempt

In CI we sometimes encouter fail of the gNB/UE deployment (and fail of
the pipeline) caused by unsuccsessful initialization of the USRP N310.
Restart the container if the health check fails during initialization.

Introduce a configurable parameter (from XML) to set max number of
attempts for the container deployment.

Store logs from failed deployment attempts.
This commit is contained in:
Jaroslava Fiedlerova
2024-12-05 14:13:22 +01:00
parent f078e6f9c7
commit f786d92bc9
7 changed files with 41 additions and 28 deletions
@@ -89,6 +89,7 @@
<yaml_path>ci-scripts/yaml_files/5g_sa_n310_2x2_100MHz</yaml_path>
<eNB_instance>0</eNB_instance>
<eNB_serverId>0</eNB_serverId>
<num_attempts>3</num_attempts>
</testCase>
<testCase id="000001">
@@ -89,6 +89,7 @@
<yaml_path>ci-scripts/yaml_files/5g_sa_n310_2x2_60MHz</yaml_path>
<eNB_instance>0</eNB_instance>
<eNB_serverId>0</eNB_serverId>
<num_attempts>3</num_attempts>
</testCase>
<testCase id="000001">
@@ -89,6 +89,7 @@
<yaml_path>ci-scripts/yaml_files/5g_sa_n310_4x4_60MHz</yaml_path>
<eNB_instance>0</eNB_instance>
<eNB_serverId>0</eNB_serverId>
<num_attempts>3</num_attempts>
</testCase>
<testCase id="000001">
@@ -80,6 +80,7 @@
<yaml_path>ci-scripts/yaml_files/5g_sa_n310_gnb</yaml_path>
<eNB_instance>0</eNB_instance>
<eNB_serverId>0</eNB_serverId>
<num_attempts>3</num_attempts>
</testCase>
<testCase id="800814">
<class>Create_Workspace</class>
@@ -93,6 +94,7 @@
<yaml_path>ci-scripts/yaml_files/5g_sa_n310_nrue</yaml_path>
<eNB_instance>1</eNB_instance>
<eNB_serverId>1</eNB_serverId>
<num_attempts>3</num_attempts>
</testCase>
<testCase id="000001">