bugfix clean-logs, avoid crushed container when folder not found

[romsharon98]

Follow up: #33162

In my case I have high available scheduler (2 schedulers).

When I upload the chart on kubernetes I got exception inside the container scheduler-log-groomer:

find: ׳/opt/airflow/logs/dag_id=example/run_id=example׳: No such file or directory
find: ׳/opt/airflow/logs/dag_id=example/run_id=example1׳: No such file or directory
...

and the container got restart.

I think it's a race condition when more then 1 scheduler runs log-grommer container and try to delete the same directory.

---

^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in newsfragments.

[romsharon98]

This fix is simple and works but the disadvantage of it that every ERR is except here.
There is other solution that will except the specific file not found exception:

error_file=$(mktemp)
find "${DIRECTORY}"/logs -type d -empty -delete

if grep -q "No such file or directory" "$error_file"; then
    cat "$error_file"
    echo "Info: if you run with hight available scheduler probably the other scheduler already delete it"
fi

rm "$error_file"

[potiuk]

Why not just find "${DIRECTORY}"/logs -type d -empty -delete || true ? That will ignore any errors. I think it should be pretty enough.

[romsharon98]

Yep. you are right. :)