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

   ### Under which category would you file this issue?
   
   Providers
   
   ### Apache Airflow version
   
   3.2.2
   
   ### What happened and how to reproduce it?
   
   To reproduce the issue:
   1. Create a dummy dag, and in access control block of the DAG, set a role 
that doesn't exist in the Airflow
   2. This DAG shows up with import errors on Airflow UI, but still in 
serialized dags table
   3. In the same container, or another container connecting to the same 
Airflow metadata DB, run `airflow sync-perm --include-dags`. It will fail with 
a FABException saying the role for that bad DAG doesn't exist, and it blocks 
permission sync for all other good DAGs.  
   
   ### What you think should happen instead?
   
   Bad/Misconfigured DAGs or non-existing roles should be ignored when running 
`airflow sync-perm --include-dags` so that it doesn't block system wide 
permission sync.
   
   ### Operating System
   
   _No response_
   
   ### Deployment
   
   None
   
   ### Apache Airflow Provider(s)
   
   fab
   
   ### Versions of Apache Airflow Providers
   
   3.6.4
   
   ### Official Helm Chart version
   
   Not Applicable
   
   ### Kubernetes Version
   
   _No response_
   
   ### Helm Chart configuration
   
   _No response_
   
   ### Docker Image customizations
   
   Official 3.2.2 docker image
   
   ### 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]

Reply via email to