-
Notifications
You must be signed in to change notification settings - Fork 687
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
Private git repos with SSH does not seem to work #2578
Comments
Hi @johnqa, As per the logs, it is saying cloned repo is empty. Can you check your cloned repo? |
Hi, If I clone my repo manually on a linux box, it is not empty. By the way, my installation is on a RKE cluster. |
which logs, the ones from litmus-portal-server? |
|
There is no difference:
When you say from the portal you mean from the UI. Is there maybe a cli way of doing things? |
Yes, I meant from the UI. Currently, we don't support private hub setup from CLI. |
I have the same error if I want to use the same repository for GitOPS. By the way, now I am using 2.00-Beta1, but I had the same issue with the stable version. |
Hi @johnqa , are you providing the SSH link of the repo. It should be something like this |
Also, For debugging purpose. Can you exec into the litmus-portal-server(graphl-server) container and try to do a git clone of your repo? I am suspecting some network/proxy issue. |
Yes I tried that but I am getting git: not found |
It's a alpine image, so you have to do |
no luck
|
Can you check with wget and curl? |
@johnqa Currently, litmusportal-server(graphql-server) container is a non-root container, that's why it is showing permission error. I just built a root image. Can you replace the graphql-server container image with After that, Can you exec into the new container and do wget of your git repo? |
Hi, I have done that, but wget from alpine doesn't allow --username and --password flags so I get 401 Unauthorized |
My git repo is not in github but in Azure DevOps Server and it looks like |
Then, Can you do the following steps ?
Before that, make sure you follow this thread #2578 (comment) |
hi @rajdas98 I cannot follow the steps as I am in air gapped environment and apk add git tries to connect to some repos that are outside this. If I try in the portal to use git@... I have another error saying: |
@johnqa if the container does not have sufficient permissions, then it may not able to read / write from / to azure repositories, since you have already added chaos charts, you may try creating a custom scope map giving read / write permissions to the chaos charts internal repo and a private ACR then upload litmus portal images to it and update their scope with the custom scope map from configurations, then the ACR may be added to RKE as a private registry, the privileged images should now be able to access the chaos charts repo on azure depending on scope map permissions. |
hi, could it be related to this? argoproj/argo-workflows#5235 |
Hi @johnqa, Looks like the same issue. But we are using the |
Hi,
What happened:
Since my litmus-portal deployment is an air gapped environment, I created a git repository in Azure DevOps Server and downloaded the https://github.com/litmuschaos/chaos-charts repo and put it in that internal one.
I am trying to add this internal repo as a private chaos hub using SSH authentication but I a, getting an error when submitting it:
If I look in the portal-server logs I see:
What you expected to happen:
I would expect to work and be able to create hubs this way.
Anything else we need to know?:
If I manually create /charts/ folder in /tmp/version/3db98aa5-7562-4d71-a2b3-8f3ff57a3a95/ and retry, the hub says it's connected with error but it's empty.
Thank you,
John
The text was updated successfully, but these errors were encountered: