-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
[BUG] GitFS fails to authenticate over SSH on Ubuntu 20.04 (focal) #58898
Comments
Hi there! Welcome to the Salt Community! Thank you for making your first contribution. We have a lengthy process for issues and PRs. Someone from the Core Team will follow up as soon as possible. In the meantime, here’s some information that may help as you continue your Salt journey.
There are lots of ways to get involved in our community. Every month, there are around a dozen opportunities to meet with other contributors and the Salt Core team and collaborate in real time. The best way to keep track is by subscribing to the Salt Community Events Calendar. |
Duplicate of #51495 This is a known issue of libssh2-1.8.0 and should be fixed in libssh2-1.8.2 via libssh2/libssh2@165f05e and libssh2-1.9.0. See also the following items:
According to reports in libssh2/libssh2#336 there are also users still seeing this issue on 1.8.2, but for most it seems to be working. |
Indeed. The issues seems to be as you describe. Unfortunately that means that Ubuntu 20.04 will not work with the libssh2 provided by the Canonical repositories. I have now installed pygit2 and libssh2 (1.9.0) manually, which fixes the problem. |
If Ubuntu were to update libssh2-1.8.0 to 1.8.2 this bug would be fixed - it's unlikely they're going to update to 1.9.0. |
Bad news for Ubuntu users - From the changelog:
This is also confirmed by looking at the
|
For Ubuntu 20.04 working solution is to run:
|
This comment has been minimized.
This comment has been minimized.
Yes, that's why I don't do that normally. It was just a debug step taken to exclude any permission issue while tracking down the original issue. I figured I'd note it in the issue to rule it out straight away. |
I tried this and it made no difference
What's weird is that it does seem to actually fetch it. Changes are visible, and salt --versions
|
Don't remember all details @OrangeDog. But on my server I have:
and:
|
I've already removed that one. I can downgrade to pygit2==1.3.0 and see if that makes any difference. |
This is an ongoing problem. I packaged the current version of pygit2 (1.6.0) and libgit2 (1.1.1), but this also leads to the behaviour described above. Installing the same module via pip works, so i'm a bit stumped how to proceed further, as installing random packages via pip is not a way to go for our production environment. Any suggestions on how to debug this further on Ubuntu 20.04? |
Description
Trying to get the GitFS backend to work keeps resulting in this error:
It takes quite long for the authentication to fail, so I suspect a timeout is reached.
Setup
Configuration
The SSH key is added as a Deploy Key to the Git repository.
Also tried:
All the attempts resulted in the same error. I am able to do a 'git clone' manually of the repository.
Steps to Reproduce the behavior
Installation is done through
apt-get
using the instructions here.Installed
python3-pygit2
package throughapt-get
After setting up the master (and a minion) with the above config.
Create a new GitHub repository with a
top.sls
file on themain
branch.Generate an SSH key and add the SSH key as a Deploy Key to the GitHub repository.
Run as root:
Expected behavior
The command succeeds
Versions Report
salt --versions-report
(Provided by running salt --versions-report. Please also mention any differences in master/minion versions.)Additional context
Also reported as a comment on this closed issue: #52636 (comment)
The text was updated successfully, but these errors were encountered: