Edit connection fields dissapearing from web interface

[suhren]

Apache Airflow version

2.9.0

If "Other Airflow 2 version" selected, which one?

No response

What happened?

We have recently upgraded from Airflow 2.4.0 to 2.9.0. The migration itself went fine, but we have noticed that the "Edit Connection" page in the Airflow web interface is not working properly when trying to edit existing connections. Specifically, when we try to edit some of our Spark connections, all available configuration fields quickly (less than a second) flash up on the page, but then dissapear. We are then left with only a small subset of fields we can edit. I have tried using incognito mode, as well as different browsers (Firefox, Chrome, Edge), but they all behave the same. I am attaching two images to show what I mean. The first image shows what we see for only a fraciton of a second when the page loads, then it quickly reverts to the fields seen in the second image.

What you think should happen instead?

No response

How to reproduce

We set up a fresh installation of Airflow 2.9.0 and added some Spark configurations like the ones seen in the images attached. When starting the web server and navigating to the "edit connections" page, we get this behavior.

Operating System

Red Hat Enterprise Linux Server 7.6 (Maipo)

Versions of Apache Airflow Providers

No response

Deployment

Virtualenv installation

Deployment details

No response

Anything else?

No response

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

[boring-cyborg]

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.

[RNHTTR]

What version of apache-airflow-providers-apache-spark do you have installed?

[suhren]

Hi @RNHTTR. I am using apache-airflow-providers-apache-spark 4.7.2

[eladkal]

I think this was fixed in #39229 ?

[github-actions]

This issue has been automatically marked as stale because it has been open for 14 days with no response from the author. It will be closed in next 7 days if no further activity occurs from the issue author.