atul-astronomer opened a new issue, #55495:
URL: https://github.com/apache/airflow/issues/55495
### Apache Airflow version
main (development)
### If "Other Airflow 2 version" selected, which one?
_No response_
### What happened?
```javascript
File "/usr/python/lib/python3.10/site-packages/urllib3/connection.py",
line 325, in connect
self.sock = self._new_conn()
File "/usr/python/lib/python3.10/site-packages/urllib3/connection.py",
line 205, in _new_conn
raise NameResolutionError(self.host, self, e) from e
urllib3.exceptions.NameResolutionError: <urllib3.connection.HTTPConnection
object at 0xffff6c254d00>: Failed to resolve 'a70a0fdb1be2' ([Errno -2] Name or
service not known)
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/python/lib/python3.10/site-packages/requests/adapters.py", line
644, in send
resp = conn.urlopen(
File "/usr/python/lib/python3.10/site-packages/urllib3/connectionpool.py",
line 841, in urlopen
retries = retries.increment(
File "/usr/python/lib/python3.10/site-packages/urllib3/util/retry.py",
line 519, in increment
raise MaxRetryError(_pool, url, reason) from reason # type:
ignore[arg-type]
urllib3.exceptions.MaxRetryError: HTTPConnectionPool(host='a70a0fdb1be2',
port=8793): Max retries exceeded with url:
/log/dag_id=attach_extra_info/run_id=manual__2025-09-11T08:07:19.739517+00:00/task_id=attach_extra_using_metadata/attempt=1.log
(Caused by NameResolutionError("<urllib3.connection.HTTPConnection object at
0xffff6c254d00>: Failed to resolve 'a70a0fdb1be2' ([Errno -2] Name or service
not known)"))
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File
"/opt/airflow/airflow-core/src/airflow/utils/log/file_task_handler.py", line
876, in _read_from_logs_server
response = _fetch_logs_from_service(url, rel_path)
File
"/opt/airflow/airflow-core/src/airflow/utils/log/file_task_handler.py", line
185, in _fetch_logs_from_service
response = requests.get(
File "/usr/python/lib/python3.10/site-packages/requests/api.py", line 73,
in get
return request("get", url, params=params, **kwargs)
File "/usr/python/lib/python3.10/site-packages/requests/api.py", line 59,
in request
return session.request(method=method, url=url, **kwargs)
File "/usr/python/lib/python3.10/site-packages/requests/sessions.py", line
589, in request
resp = self.send(prep, **send_kwargs)
File "/usr/python/lib/python3.10/site-packages/requests/sessions.py", line
703, in send
r = adapter.send(request, **kwargs)
File "/usr/python/lib/python3.10/site-packages/requests/adapters.py", line
677, in send
raise ConnectionError(e, request=request)
requests.exceptions.ConnectionError: HTTPConnectionPool(host='a70a0fdb1be2',
port=8793): Max retries exceeded with url:
/log/dag_id=attach_extra_info/run_id=manual__2025-09-11T08:07:19.739517+00:00/task_id=attach_extra_using_metadata/attempt=1.log
(Caused by NameResolutionError("<urllib3.connection.HTTPConnection object at
0xffff6c254d00>: Failed to resolve 'a70a0fdb1be2' ([Errno -2] Name or service
not known)"))
```
### What you think should happen instead?
_No response_
### How to reproduce
1. Start airflow with version 2.11.0
2. Run a few dags and verify user is able to see the task logs
3. Stop_airflow and start the airflow without giving any version, it will
migrate to the latest.
4. Click on the task_id of the dagruns which were created in previous
airflow version and notice the error in API server.
### Operating System
Linux
### Versions of Apache Airflow Providers
_No response_
### Deployment
Other
### Deployment details
_No response_
### 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]
