Bug on airflow of Openmetadata

hoang09011996 commented 6 months ago

Checks

[X] I have checked for existing issues.
[X] This report is about the Openmetadata Helm Chart.
[X] This report is about the Openmetadata Dependencies Helm Chart.

Description

Bug Description: When install openmetadata-dependencies. after it done. i have this bug. after that. when using OM ingres metadata from other source. this worker of airflow always error. I think this is some misstake in here. How can i fix it.

Steps to reproduce

No response

Chart Version

new

App Version

new

Kubernetes Version

v1.26.5

Helm Version

v3.13.2

Relevant Logs

No response

Custom Helm Values

No response

Have you joined Openmetadata Slack community?

Yes

Doritanh commented 4 months ago

Hello, I have exactly the same problem. Have you by any chance found a solution?

From what I've seen, the airflow_lineage_operator.py script requests the connection /api/v1/connections/openmetadata_conn_id to localhost:8080, which doesn't work because it's a pod and airflow is on another pod.

HTTPConnectionPool(host='localhost', port=8080): Max retries exceeded with url: /api/v1/connections/openmetadata_conn_id

Regards,

FleischerT commented 3 months ago

Unfortunately, we have exactly the same problem. With the latest version of the charts as well as with version 1.3.3. Has anyone been able to solve the problem?

hoang09011996 commented 3 months ago

@Doritanh, @FleischerT . I resolved the error. The issue was with the MySQL chart in the Helm chart, which had an error I couldn't fix. You can find the log on the MySQL pod; it contains a warning. When I tried deploying a new MySQL database for Airflow and OP, the error was resolved.

open-metadata / openmetadata-helm-charts