amoghrajesh commented on PR #60270: URL: https://github.com/apache/airflow/pull/60270#issuecomment-3727515054
I think the problem is basically that: 1. When running as AIRFLOW user, bundle init happens as part of `parse` and all locks are created as AIRFLOW user 2. If run_as_user is set, current process exits and is replaced by new one with impersonated user 3. When running with that user, when `parse` is retried, bundle was inited earlier, so it is just loaded, and while trying to load it, permission conflict comes in, and lock cannot be acquired. Why can we not consider initing the bundle after we know "who" will run the task? Maybe an early pass to detect "run_as_user" and then actually init the bundle with that user? -- 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]
