jonathanjuursema commented on issue #28010: URL: https://github.com/apache/airflow/issues/28010#issuecomment-1359360159
Hey! Thanks for checking back. I think we're confusing two things here. The test with the `banana` hostname was in response to the following challenge: > Raising an exception in your config and seeing it in your logs will make sure you have not made any typo or problem I've set the hostname to something non-existent, to validate it does indeed load the configuration. Because the worker throws the "name or service not known" error, it seems to correctly load the (invalid) config. The scheduler and web server however, don't seem to, as they would otherwise also have thrown this or a similar exception. Just to be sure, I've also validated name resolution with the actual domain names that I'm having the problems with (the internal information redacted with `xxx`). This works as expected: ``` (airflow)host xxx xxx has address 10.120.xxx.xxx ``` Finally, I'm positive we can rule out firewalling. There are other applications running on the same virtual machines that can access those Redis Sentinal instances just fine. Our Redis firewalls are configured to accept all incoming connections from the virtual machines Airflow (and those other apps) are running on. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
