ryan-podfoods commented on issue #31743: URL: https://github.com/apache/airflow/issues/31743#issuecomment-1580876331
> Hi, > > I have the exact same issue. > > However, I have some additional context that might be beneficial. This seems to me like an issue with the triggerer not being in sync. This is further confirmed by my local instance (simple dockerized setup) not having this issue at all (just some folders being mounted to the containers instead of a gitsync container). > > For example, if you change the name of the apply_function you will notice you get the exact same issue (without changing the file name). I have checked on my instance and the gitsync container for the triggerer is running without issues (atleast from the logs). > > I have further investigated this by doing the following actions : > > 1. A working DAG using the apply_function without issues > 2. Changed the DAG to use a different apply_function ; tested and failed as it could not import the function. (same error as above) > 3. downscaled the triggerer statefulset (to 0) and back to 1 (effectively recreating the containers). > 4. Ran the DAG (which was failing) once again, it now runs without issues. > > To me it seems that the DAG on the Triggerer side is not correctly being synced to be in line with what is on the web UI/worker. This is very weird as I have checked the trigger-gitsync container logs to see whether a refresh was done and it did log a refresh. > > *edit : obviously it should not be necessary to recreate a container in order to get this updated. I am also observing similar behavior. Triggers are not updated for me until the Pod is recreated. GitSync sidecar appears to run once and terminates, I'm assuming because the environmental variable `GIT_SYNC_ONE_TIME` is set to `true`. Triggerer continues to function as expected, just with out of sync code for me. -- 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]
