-
Notifications
You must be signed in to change notification settings - Fork 14.5k
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
airflow is not accepting configuration from Admin UI #16810
Comments
Can't use my PC at the moment but it does look awfully a lot like we need to release 2.1.2 with a fix if it is confirmed @ashb @kaxil @jhtimmins |
Agreed, will confirm. |
Got hold of my PC. Confirmed that it does not occur in main but it DOES occur in 2.1.1. |
I have a fix (conf-> run_conf) - likely bad cherry-pick. Looking at why it has not been caught by the test_harness (the tests for dag triggering seem to pass :(. |
There was a bad cherry-pick when merging apache#15057 that has not been caught because of quarantined test. Fixes: apache#16810
Looks like we already had a fix: #16648 |
Yep. That's it. Also it has not been caught in the tests because the test was quarantined. Looks like we need to take a close look at the quarantined tests and fix them. |
I have cherry-picked it to v2-1-stable and v2-1-test, we will cut a 2.1.2 release which should be available to the users by the end of this week. Until then, please use the API or CLI to trigger dags. |
Closing this issue as the fix is merged and it will be released soon. |
This test caused missing failure that manifested in 2.1.1 in the apache#16810
This test caused missing failure that manifested in 2.1.1 in the apache#16810
This test caused missing failure that manifested in 2.1.1 in the #16810
Apache Airflow version: 2.1.1
Kubernetes version (if you are using kubernetes) (use
kubectl version
): NOEnvironment: local (docker + ubuntu)
uname -a
): linuxWhat happened:
airflow is not accepting configuration from Admin UI
when I submit a DAG configuration from UI, it is giving me error
Invalid JSON configuration, must be a dict
the same workflow is working in airflow 2.1.0 version
I think this issue occurred in this PR #15057
What you expected to happen:
Airflow admin should accept the conf from UI and trigger the dag
How to reproduce it:
It can be reproduced for all cases, we have to put any valid JSON into the configuration window on a DAG
Willing to submit PR
YES
The text was updated successfully, but these errors were encountered: