V0lantis opened a new pull request, #24999: URL: https://github.com/apache/airflow/pull/24999
<!-- Thank you for contributing! Please make sure that your code changes are covered with tests. And in case of new features or big changes remember to adjust the documentation. Feel free to ping committers for the review! In case of an existing issue, reference it using one of the following: closes: #ISSUE related: #ISSUE How to write a good git commit message: http://chris.beams.io/posts/git-commit/ --> Fix a scheduler `crashLoopBackOff` when `hostname_callable` was defined with a function which returned something different than the `hostname` command from linux. In our production Airflow, I updated the [`hostname_callable`](https://airflow.apache.org/docs/apache-airflow/stable/configurations-ref.html#hostname-callable) config with [`airflow.utils.net.get_host_ip_address`](https://github.com/apache/airflow/blob/a3f2df0f45973ddb97990361fdc5caa256c175ca/airflow/utils/net.py#L46-L48). But this new config was making kubernetes to restart the scheduler pods because the [command defined in helm](https://github.com/apache/airflow/blob/451181f6f2efd8b5e6bd7807e84a17d48a4fe875/chart/templates/_helpers.yaml#L640-L641) was returning a "No alive jobs found." I therefore updated the cli command jobs to allow the use of `--use-hostname-callable` in: ```bash airflow jobs check --job-type SchedulerJob --use-hostname-callable ``` to use the `hostname_callable` that the user defined in its Airflow conf. Also updated the helm chart to with this new conf since I think it will be more reliable than to use linux `hostname` command. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
