Sozik87 opened a new issue, #63945:
URL: https://github.com/apache/airflow/issues/63945
### Apache Airflow version
3.1.8
### If "Other Airflow 3 version" selected, which one?
_No response_
### What happened?
Hello dear friends!
Today I updated Airflow from 3.1.5 to 3.1.8. The "airflow db migrate" were
also performed in our k8s. After that, launching DAG's and reading logs was no
longer possible.
The container logs contain errors like:
**_"httpcore.ConnectError: [Errno -2] Name or service not known"_**
In the UI, I see this:
**Log message source details sources=["Could not read served logs: Invalid
URL
'http://:8793/log/dag_id=test_dag_check/run_id=scheduled__2026-03-19T07:35:00+00:00/task_id=send_command/attempt=1.log'
: No host supplied"]**
It seems that he stopped receiving "_hostname_" after this update.
I also tried to specify it in **airflow.cfg**:
**[core]
hostname_callable = airflow.utils.net.get_host_ip_address**
But the problem repeats.
I'm sorry, that's all I can point out at the moment.
Maybe someone has encountered the same thing?
And an additional question, can I do:
**airflow db downgrade --to-version 3.1.5** so that I can return to the
working version 3.1.5?
Thank you for helping!
### What you think should happen instead?
DAG's must be executed, logs must be visible
### How to reproduce
1. Update the airflow package from 3.1.5 to 3.1.8 in the Dockerfile
2. Launch the init container with "**airflow db migrate**"
3. Try to run the DAG
### Operating System
ubuntu:22.04
### Versions of Apache Airflow Providers
I use several packages from
https://raw.githubusercontent.com/apache/airflow/constraints-3.1.8/constraints-3.10.txt
### Deployment
Other Docker-based deployment
### Deployment details
helm,k8s
### Anything else?
_No response_
### Are you willing to submit PR?
- [ ] Yes I am willing to submit a PR!
### Code of Conduct
- [x] I agree to follow this project's [Code of
Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
--
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]
