kata-deploy: Stop append log_level = "debug" for CRI-O

This should only be done once, and if CRI-O restarts, there's a big
chance kata-deploy will also restart and the user would end up with a
file that looks like:
```
[crio]
log_level = "debug"
[crio]
log_level = "debug"
[crio]
log_level = "debug"
...
```

And that would simply cause CRI-O to not start.

Signed-off-by: Fabiano Fidêncio <fabiano.fidencio@intel.com>
This commit is contained in:
Fabiano Fidêncio 2024-04-22 09:49:27 +02:00
parent 42a79801f3
commit d190c9d4d9
No known key found for this signature in database
GPG Key ID: EE926C2BDACC177B

View File

@ -341,6 +341,8 @@ function configure_crio() {
mkdir -p "$crio_drop_in_conf_dir"
rm -f "$crio_drop_in_conf_file"
touch "$crio_drop_in_conf_file"
rm -f "$crio_drop_in_conf_file_debug"
touch "$crio_drop_in_conf_file_debug"
for shim in "${shims[@]}"; do
configure_crio_runtime $shim
@ -348,7 +350,7 @@ function configure_crio() {
if [ "${DEBUG}" == "true" ]; then
cat <<EOF | tee -a $crio_drop_in_conf_file_debug
cat <<EOF | tee $crio_drop_in_conf_file_debug
[crio]
log_level = "debug"
EOF