Hello there! You are receiving this message because none of your fellow community members has stepped in to respond to your topic post. (If you are a community member and you are reading this response, feel free to jump in if you have the answer!) As a result, the Community Assistance Team has been made aware of this topic and will be investigating and responding as quickly as possible.
Some important considerations that will help your to get your issue solved faster:
It is best to use our topic creation template; if you haven’t yet, we recommend posting a followup with the requested information. With that information the team will be able to more quickly search for similar issues with connectors and the platform and troubleshoot more quickly your specific question or problem.
Make sure to upload the complete log file; a common investigation roadblock is that sometimes the error for the issue happens well before the problem is surfaced to the user, and so having the tail of the log is less useful than having the whole log to scan through.
Be as descriptive and specific as possible; when investigating it is extremely valuable to know what steps were taken to encounter the issue, what version of connector / platform / Java / Python / docker / k8s was used, etc. The more context supplied, the quicker the investigation can start on your topic and the faster we can drive towards an answer.
We in the Community Assistance Team are glad you’ve made yourself part of our community, and we’ll do our best to answer your questions and resolve the problems as quickly as possible. Expect to hear from a specific team member as soon as possible.
Thank you for your time and attention.
The Community Assistance Team
I experienced the same issue with trying to upgrade an existing Kubernetes instance using Helm and the v0.44.0 and v0.44.1 charts from airbytehq.github.io.
I was able to resolve the issue by editing the <RELEASE_NAME>-airbyte-env configmap in Kubernetes to include the keys “STRICT_COMPARISON_NORMALIZATION_TAG” and “STRICT_COMPARISON_NORMALIZATION_WORKSPACES” with empty strings as values. Then I deleted the worker pod that was failing to start and the recreated pod started. Airbyte appears functional again.
I noted this and this commit to master concerning flags with these values. It is somewhat confusing because the first commit Reverts a commit that added these flags to charts/airbyte-worker/templates/deployment.yaml (along with other places the flags are picked up) and the second commit Reverts the reversion.
Perhaps related, the Helm chart version I am getting from the official Helm repo is 0.44.1 but on master in the Github Airbyte repo, the chart version in charts/airbyte/Chart.yaml is 0.43.22. I am curious if there is any insight into how Chart versions on airbytehq.github.io relate to the versions on master in the Airbyte repo.