zachliu opened a new issue, #49651:
URL: https://github.com/apache/airflow/issues/49651
### Apache Airflow version
3.0.0
### If "Other Airflow 2 version" selected, which one?
_No response_
### What happened?
I've just started noticing this behavior in Airflow 3.0.0:
* The `role does not exist` errors no longer persist in the "DAG Import
Errors" section of the UI, nor in the database.
For example, I have
```python
dag.access_control = {"non_existing_role": {"can_edit", "can_read"}}
```
in many DAGs. These `role does not exist` errors do initially appear in the
"DAG Import Errors," but only briefly. After a few minutes, they disappear—you
can no longer find them in the UI, the logs, or the database. The dag-processor
logs show successful parsing for all DAGs that still contain the
`non_existing_role`.
The only way to surface the same error message again is by running `airflow
sync-perm --include-dags -v` inside the container.
I vaguely recall that these types of errors used to persist in the "DAG
Import Errors" section in versions prior to and including `3.0.0rc2`.
(Other parsing errors, such as ill-formatted Variables, do not appear to
exhibit this issue.)
Here is a screenshot of the error before it disappeared:
### What you think should happen instead?
The `role does not exist` error should persist until the role is created.
### How to reproduce
Use `access_control` with a non-existing role name in any DAG(s):
```python
dag.access_control = {"non_existing_role": {"can_edit", "can_read"}}
```
### Operating System
LM 21.3 with docker python:3.12-slim-bookworm
### Versions of Apache Airflow Providers
_No response_
### Deployment
Docker-Compose
### Deployment details
_No response_
### 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]
