Ignore error when changing log folder permissions

[potiuk]

In some circumstances, changing the permission of a parent folder for the log might not be possible - for example when it was created by another user (with impersonation) or when the filesystem does not allow for permission change.

Fixes: #29112

---

^ 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.

[potiuk]

cc: @SamWheating

[potiuk]

I am also marking it as 2.5.3 - although it will not be super-easy to cherry-pick that one due to earlier changes from #27758 and related chnges, but it should be possible to apply the same workaround in the same cod (cc: @pierrejeambrun @ephraimbuddy ) . This seems to affect some common cloud cluster cases by default, so it might be worth the hassle (happy to help with cherry-picking if needed then).

[potiuk]

BTW. It also could be that @SamWheating's change from #29886 would also address the problem in some cases - maybe simply after checking the mask, the chmod would not have happened at all (when the filesystem is such that it has "open write for all" by default.

[thesuperzapper]

@potiuk I am still seeing many users report errors in airflow 2.5.3 as this change was not back-ported.

The error is always associated with this line airflow/utils/log/file_task_handler.py#L358, perhaps we can put a temporary fix for 2.5.4 which puts a try/catch around that (and any other chmod attempts).

[potiuk]

There won't be a 2.5.4 most likely - we are just about to release 2.6.0 and preparing for it.