OscarLigthart opened a new issue, #60600:
URL: https://github.com/apache/airflow/issues/60600

   ### Apache Airflow Provider(s)
   
   google
   
   ### Versions of Apache Airflow Providers
   
   19.3.0
   
   ### Apache Airflow version
   
   3.1.6
   
   ### Operating System
   
   Debian GNU/Linux 12 (bookworm)
   
   ### Deployment
   
   Other 3rd-party Helm chart
   
   ### Deployment details
   
   _No response_
   
   ### What happened
   
   After upgrading to 3.1.6, we started seeing the following error in our 
GKEStartPodOperator execution, running in `deferred` mode:
   
   ```
   AttributeError: 'GKEKubernetesAsyncHook' object has no attribute 
'_event_polling_fallback'
   File 
"/home/airflow/.local/lib/python3.12/site-packages/airflow/providers/cncf/kubernetes/triggers/pod.py",
 line 161 in run
   
   File 
"/home/airflow/.local/lib/python3.12/site-packages/airflow/providers/cncf/kubernetes/triggers/pod.py",
 line 262 in _wait_for_pod_start
   
   File 
"/home/airflow/.local/lib/python3.12/site-packages/airflow/providers/cncf/kubernetes/utils/pod_manager.py",
 line 1018 in watch_pod_events
   
   File 
"/home/airflow/.local/lib/python3.12/site-packages/airflow/providers/cncf/kubernetes/hooks/kubernetes.py",
 line 1001 in watch_pod_events
   ```
   
   ### What you think should happen instead
   
   The `GKEKubernetesAsyncHook` should have an attribute 
`_event_polling_fallback`, as it is part of the initialization method of 
`AsyncKubernetesHook`.
   
   ### How to reproduce
   
   In our case, we run tasks with the GKEStartPodOperator in `deferred` mode. 
The pod runs without issues to completion, but tasks are marked as failed with 
the exception stated above.
   
   ### Anything else
   
   _No response_
   
   ### Are you willing to submit PR?
   
   - [x] 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]

Reply via email to