-
Notifications
You must be signed in to change notification settings - Fork 14.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pause/unpause dag logs wrong event status #31871
Comments
Thanks for opening your first issue here! Be sure to follow the issue template! If you are willing to raise PR to address this issue please do so, no need to wait for approval. |
hi, ANy update on the issue, |
Since you checked in |
yes, I want to open PR. |
Assigned you then :) |
any luck you are able to find. |
not sure if this is related but in this version 2.5.1 when we try to pause a dag programatically the value is not logged to the audit logs if it runs by the scheduler. |
Able to reproduce this on main branch |
@eladkal Would you be able to review the PR I opened a few days ago? 🙏 |
Solved in #36182 |
Apache Airflow version
Other Airflow 2 version (please specify below)
What happened
IN version 2.5.1 release, airflow pause/unpause dag button on dags page doesn't work properly.
When we pause a dag in the audit logs its show dag as unpaused.
and when we unpause any dag audit log shows a dag is paused. Also sometimes dag runs properly as per schedule and sometime doesn't because of this problem.
IN recent dag behaviour, we enabled the dag on friday and dag was scheduled to run on Monday but it didn't. It was a active dag not paused in blue color. However in the dag audit logs, it was showing below :
What you think should happen instead
when we pause, it should say its paused, when we unpause or resume, it should give message that dag is in unpause or resume state.
How to reproduce
try, for me this is still live problem in 2.5.1
Operating System
centos 7
Versions of Apache Airflow Providers
No response
Deployment
Official Apache Airflow Helm Chart
Deployment details
No response
Anything else
No response
Are you willing to submit PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: