airbytehq / airbyte

The leading data integration platform for ETL / ELT data pipelines from APIs, databases & files to data warehouses, data lakes & data lakehouses. Both self-hosted and Cloud-hosted.
https://airbyte.com
Other
15.88k stars 4.07k forks source link

can't delete connections through UI #9674

Closed answerMA closed 2 years ago

answerMA commented 2 years ago
## Environment - **Airbyte version**: example is 0.35.5-alpha - **OS Version / Instance**: Centos7 - **Deployment**: Docker - **Source Connector and version**: (if applicable example Salesforce 0.2.3)

Current Behavior

as I clicked "delete this connection" in the connection setting page, and confirmed to delete, then nothing happened. the connection still exists

Expected Behavior

connections should be deleted

Logs

If applicable, please upload the logs from the failing operation. For sync jobs, you can download the full logs from the UI by going to the sync attempt page and clicking the download logs button at the top right of the logs display window.

LOG ``` replace this with your long log output here ```

Steps to Reproduce

1. 2. 3.

Are you willing to submit a PR?

Remove this with your answer.

cgardens commented 2 years ago

@answerMA thanks for reaching out. if you refresh the page does it go away. i think there's a known caching issue in the UI.

wjmolina commented 2 years ago

It doesn't go away even if you refresh the UI. In fact, when I click on its "Sync now" button, I get the message

Something went wrong
Internal Server Error: The connection manager workflow for connection 96310eb8-f96c-4d63-b69c-244a4940a73b is deleted, so no further operations cannot be performed on it.

It doesn't look like a caching issue because the connection still exists in the connection table of the Airbyte database.

mattppal commented 1 year ago

I'm having the same issue

wjmolina commented 1 year ago

I'm having the same issue

You could set the status of the offending connection to deprecated in the Airbyte database.

craunas commented 1 year ago

Im getting the same error message on v.44.2 when generating connections with Octavia CLI. The connections was orginally created v0.40.29 and I wanted to move them to an Airbyte instance on a newer version.

Had a quick look in the db and one thing I noticed was that the connections created manually on the new version got an source_catalog_id referring to an entry in public.actor_catalog.

The connections imported by Octavia was missing source_catalog_id.

Any workaround or solution for this?

katesclau commented 2 months ago

I had a similar issue, where the connection manager and the connection were unresolved, and the only thing that fixed it for me was to delete the connection from the Airbyte db hard. After that, I was able to recreate the connection.