Using the Run button on the Task modal results in restartPolicy of the KubernetesExecutor being set to Always

[el-aasi]

Apache Airflow version

Other Airflow 2 version (please specify below)

What happened

Usually when needing to restart a task, our users would clear the state of the given task and let the scheduler deal with it. Some of the new users - intuitively would press the Run button on the task instead of Clearing the state this would result in a KubernetesExecutor being created with the restart policy set to Always as well as failing with:

airflow.exceptions.AirflowException: Dag 'DAG NAME' could not be found; either it does not exist or it failed to parse.

even tho all the subsequent runs worked fine without altering the dag file.

Now we have corrected that by instructing the user to clear the state when wanting to restart a task.

But we are still unsure what exactly the functionality of the Run button should be and if it is intentional for it to set the restart policy to Always.

A bit similar to this

What you think should happen instead

To be honest, I couldn't fined a specific explanation of what the Run button should do - or in what use cases it should be used - as one cannot just set the state of the task to running without going through the normal workflow.

How to reproduce

I am unsure if it is an issue specific to our cluster or our dags, but having a dag that failed at some task and trying to re-run the failed task using the Run button.

Operating System

Debian GNU/Linux 11 (bullseye)

Versions of Apache Airflow Providers

apache-airflow-providers-amazon==6.0.0
apache-airflow-providers-celery==3.0.0
apache-airflow-providers-cncf-kubernetes==4.4.0
apache-airflow-providers-common-sql==1.2.0
apache-airflow-providers-docker==3.2.0
apache-airflow-providers-elasticsearch==4.2.1
apache-airflow-providers-ftp==3.1.0
apache-airflow-providers-google==8.4.0
apache-airflow-providers-grpc==3.0.0
apache-airflow-providers-hashicorp==3.1.0
apache-airflow-providers-http==4.0.0
apache-airflow-providers-imap==3.0.0
apache-airflow-providers-microsoft-azure==4.3.0
apache-airflow-providers-mysql==3.2.1
apache-airflow-providers-odbc==3.1.2
apache-airflow-providers-postgres==5.2.2
apache-airflow-providers-redis==3.0.0
apache-airflow-providers-sendgrid==3.0.0
apache-airflow-providers-sftp==4.1.0
apache-airflow-providers-slack==6.0.0
apache-airflow-providers-sqlite==3.2.1
apache-airflow-providers-ssh==3.2.0

Deployment

Other 3rd-party Helm chart

Deployment details

User Community Airflow Helm Chart v8.7.0
AKS cluster v 1.26.3
Airflow Version v2.4.3
Airflow Git Version .release:2.4.3+c53a3e153f0ab5ca933a94adc01dc6314ea8d4d1

Anything else

Every time the Run button is used (with Ignore All Deps set)

Are you willing to submit PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

[potiuk]

The "run task" button has been removed because a) it was confusing b) it did not work in all cases c) it was dangerous to use d) there were security vulnerabilities connected to it.

See the announcement that we've just sent about it https://lists.apache.org/thread/j2nkjd0zqvtqk85s6ywpx3c35pvzyx15

So yeah you are right it made no sense to have it.

I recommend to upgrade to latest 2.6 in general to get rid of it.

[potiuk]

Closing as it has been completed in 2.6.0 already,

[el-aasi]

@potiuk awesome, thank you