gr8web commented on issue #58717: URL: https://github.com/apache/airflow/issues/58717#issuecomment-5114706236
> That means that either the dag processor did not parse the dag file at all probably, because it did not find the file for some reason, how are you using the git bundle? how are you mounting (if at all) the dag code to the dag processor? What kind of file system are you using? (I.e NFS os similar or block storage ot local storage) How many parsing processes does the processor have? > > It seems like they arearked as stale and removed immediately because the dag processor did not parse them at all and probably thinks the files where removed, do you encounter any permission denied errors or file not found errors? No mounting is involved, processor has 2 processes. The dags are checked out to the default `tmp` location on the processor pod. > do you encounter any permission denied errors or file not found errors? No, I didn't see any logs for that. At the debug level there I see only this one: ``` 2026-07-29T07:31:02.455432Z [debug ] Not syncing DAG-level permissions for DAG 'bla' as access control is unset. [airflow.providers.fab.www.security_appless.ApplessAirflowSecurityManager] loc=override.py:1010 ` -- 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]
