-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SSH control host port setting not used when tunneling #13758
Comments
Thanks for reporting this @wesen, are you going to submit a PR to fix it? The issue happens when you use. a custom port different from 22 right? |
@marcosmarxm I can make a PR. The thing is that I don't really have time to set up airbyte locally for testing, I wanted to use the SaaS version (because I don't have the time). Do you want me to open a PR still? |
SaaS = Airbyte Cloud? I think it's valid to you open the PR, team can help reviewing and doing the test. |
@marcosmarxm thanks, will do |
In Airbyte Cloud, the SSH tunnel port option is not used when using a port different than 22. This adds support for the tunnel_port option to the sshtunneling.sh script. This patch is untested, because I don't have time to setup a local test environment (this is the reason to use cloud in the first place). A more detailed bug report can be found at airbytehq#13758.
@wesen do you mind sending a message in Intercom to get help from our cloud support team? |
@wesen I have created a cloud ticket for our engineers to dig into when this connector is prioritized! It is currently in the alpha stages so I do not have an ETA but if I have any updates I will reach out! Also, thank you so much for your investigation! As Marcos mentioned, if you ever have question or need help investigating Airbyte cloud issues please do not hesitate to reach out to the Cloud support team by select "Support" in the bottom left corner of the platform and chatting in or opening a case! |
@alexandr-shegeda moving this to JGL team. The tasks here are:
|
thanks a lot @erica-airbyte and @grishick! Is there anything else you might need from me right now? |
@wesen Not at the moment! You can follow along here or I can circle back when there is an update! |
With last update from master normalization and fix is working |
What is the best way to try this out? I rebased on master and ran the stack with
Is there a way to point it to use another image? I tried to muck around with it a bit last week but sadly I don't know enough to figure out where that docker image value is set. |
Environment
Current Behavior
The sync script does not use the tunnel_port setting. This happens in sshtunneling.sh I believe. We have ssh running on port 2222 but the script connects to port 22.
Expected Behavior
The sync script should setup the ssh tunnel to the correct port.
Logs
logs-241062.txt
Steps to Reproduce
Are you willing to submit a PR?
Yes. Patch attached.
ssh-tunnel-port.patch.txt
The text was updated successfully, but these errors were encountered: