For those who are facing

Unable to resolve host airbyte-temporal

issue while local deployment: I managed to find a way to fix this issue. The problem was that airbyte-temporal server failed to start because it couldn’t find /airbyte/temporal/dynamicconfig/development.yaml file. I think this should be created by default but somehow it didn’t exist when I followed the local deployment instructions. I created an empty file with the name development.yaml in the /airbyte/temporal/dynamicconfig directory and this resolved the issue. Hope this helps

Thank you for sharing your solution to the

Unable to resolve host airbyte-temporal

issue. It's great to hear that creating an empty

development.yaml

file in the

/airbyte/temporal/dynamicconfig

directory resolved the issue for you. However, it's important to note that this solution is not mentioned in the provided extracts from the official Airbyte documentation, forum discussions, or Slack support conversations. Therefore, while it may have worked in your specific case, it might not be a universal solution for all users experiencing this issue. For users who are facing similar issues, it's recommended to check the official [Airbyte troubleshooting guide](https://docs.airbyte.com/troubleshooting) or reach out to the Airbyte community on [Slack](https://slack.airbyte.io) for further assistance.

Hello @Dave the version 0.50.10 should fix the issue

Thanks for the comment @Marcos Marx (Airbyte) but I actually encountered this issue with v0.50.11 and v0.50.10 as well

Same here

Same here

Hello @Jeffrey Hunt and @Brad Forsyth are you deploying using k8s or docker?

Docker for me

Docker

Thank you for the feedback, can you both help our team to investigate what is causing the problem and share logs and what steps you executed until hit the problem adding info in this issue? https://github.com/airbytehq/airbyte/issues/28629

Sure, will try to recreate this evening.

^ i think i'm also running into this issue deploying on docker in gcp vm using version 0.50.11, what logs should i pull to verify?

Hello, the team is actively working to fix the issue. Any update return to you asap!

Excellent. I had done the fix by manually adding an empty file to the directory, but this is obviously preferable! Thanks for the quick response. Really appreciated.

Thanks @Dave! We recreated the file manually and it solve the issue. ❤️

Hello Marcos i am following steps based on https://docs.airbyte.com/deploying-airbyte/on-aws-ec2/ and running updated ./run-ab-platform.sh -b script and still facing same issue " Failed to resolve name. status=Status{code=UNAVAILABLE, description=Unable to resolve host airbyte-temporal, cause=java.lang.RuntimeException: java.net.UnknownHostException: airbyte-temporal"

Did you get the latest version of the scripted?

yes...VERSION=0.50.11 i am setting up on amazon linux ec2 instance 2023-07-25 163132 INFO i.t.s.WorkflowServiceStubsImpl(<init>):86 - Created WorkflowServiceStubs for channel: ManagedChannelOrphanWrapper{delegate=ManagedChannelImpl{logId=19, target=airbyte-temporal:7233}} Jul 25, 2023 43132 PM io.grpc.internal.ManagedChannelImpl$NameResolverListener handleErrorInSyncContext WARNING: [Channel<19>: (airbyte-temporal:7233)] Failed to resolve name. status=Status{code=UNAVAILABLE, description=Unable to resolve host airbyte-temporal, cause=java.lang.RuntimeException: java.net.UnknownHostException: airbyte-temporal

couldn’t find /airbyte/temporal/dynamicconfig/development.yaml file

This is happening in

0.50.18

, attempting suggested fixes