Skip to content
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

Fix git-init failure with git ssh creds 🔑 #804

Merged
merged 1 commit into from
Apr 26, 2019

Conversation

vdemeester
Copy link
Member

Changes

In case of a private git resources that uses ssh keys, git
wouldn't find the correct .ssh/known_hosts. This only happens in
case of the user of the container is root.

We now treat use root as a special case. It should now work for any
user — being root or not.

Fixes #803

/cc @chmouel @dlorenc @bobcatfish

  • Backport to release-v0.3.0 branch

Signed-off-by: Vincent Demeester vdemeest@redhat.com

Submitter Checklist

These are the criteria that every PR should meet, please check them off as you
review them:

See the contribution guide
for more details.

Release Notes

Fix git-init failures with git ssh credentials

@googlebot googlebot added the cla: yes Trying to make the CLA bot happy with ppl from different companies work on one commit label Apr 26, 2019
@tekton-robot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: vdemeester

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@tekton-robot tekton-robot added approved Indicates a PR has been approved by an approver from all required OWNERS files. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Apr 26, 2019
In case of a private git resources that uses `ssh` keys, `git`
wouldn't find the correct `.ssh/known_hosts`. This only happens in
case of the user of the container is `root`.

We now treat use `root` as a special case. It should now work for any
user — being root or not.

Signed-off-by: Vincent Demeester <vdemeest@redhat.com>
@abayer
Copy link
Contributor

abayer commented Apr 26, 2019

/lgtm

@tekton-robot tekton-robot added the lgtm Indicates that a PR is ready to be merged. label Apr 26, 2019
@tekton-robot tekton-robot merged commit 0dd031e into tektoncd:master Apr 26, 2019
@bobcatfish
Copy link
Collaborator

Backport to release-v0.3.0 branch

@vdemeester I made a v0.3.1 release, lemme know if this isn't the way we want to go - we could re-release 0.3.0 but folks who have the current/broken 0.3.0 would be left in a strange state

@mgreau
Copy link
Contributor

mgreau commented Apr 27, 2019

It's great to have a v0.3.1, thanks for doing it so quickly 👍
I think it's better not to re-release the v0.3.0.

@chmouel
Copy link
Member

chmouel commented Apr 27, 2019

Thanks a lot @vdemeester to fix this up so quickly

@vdemeester vdemeester deleted the 803-git-init-failure branch April 27, 2019 07:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cla: yes Trying to make the CLA bot happy with ppl from different companies work on one commit lgtm Indicates that a PR is ready to be merged. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

SSH authentication (Git) does not work anymore
7 participants