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

   ### Apache Airflow version
   
   2.4.2
   
   ### What happened
   
   I am using cluster policy feature to add callback for all the dag. So I have 
used dag_policy function and added the callback to be invoked for success and 
failure.
   
   Case 1: Added failure callback via cluster policy and ran DAG(which fails). 
No callback is invoked
   
   Case 2: Added failure callback locally in DAG and ran DAG. Callback for 
failure case is invoked.
   
   Case 3: Added failure callback locally in DAG and via cluster policy too. 
Then ran the DAG. Now both local callback and callback added via cluster policy 
got executed.
   
   ### What you think should happen instead
   
   When callback for DAG is added via cluster policy, it has to get executed.
   
   ### How to reproduce
   
   This is the cluster policy I have added
   https://gist.github.com/Bowrna/1994894beea39fa8e1c269591b7f0346
   
   This is the test dag I have tried running
   https://gist.github.com/Bowrna/7fdca8b546fc274edd068ffdae5b76f9
   
   
   
   ### Operating System
   
   macOS Monterey 12.2.1
   
   ### Versions of Apache Airflow Providers
   
   apache-airflow-providers-apache-hive==4.0.1
   apache-airflow-providers-cncf-kubernetes==4.4.0
   apache-airflow-providers-common-sql==1.2.0
   apache-airflow-providers-ftp==3.1.0
   apache-airflow-providers-http==4.0.0
   apache-airflow-providers-imap==3.0.0
   apache-airflow-providers-sqlite==3.2.1
   
   ### Deployment
   
   Virtualenv installation
   
   ### Deployment details
   
   I am using development setup and trying to use cluster policy with callback 
added
   
   ### 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