-
Notifications
You must be signed in to change notification settings - Fork 197
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
TektonHub CR not able to clone #2072
Comments
@PuneetPunamiya please take a look at this |
@Elyytscha I tried to reproduce this issue, but was not able to reproduce it. All pods were up and running. Also seeing your error it seems like it was a network issue error. Can you try it once if you can still reproduce it ? |
I can still reproduce it:
|
Have you upgraded Hub from previous version or did you fresh install Hub ? |
i freshly installed the hub, it happens everyime i want to install the hub from scratch |
I tried this again by fresh installing hub, i don't see any issue |
I can confirm with Tekton Operator v0.70.0 its now getting past this step, now it syncs the task repo successfully as I interpret the logs. but it still shows: should I open a new issue regarding this? i attached the logs for now over here |
Can you hit this url and check if you can see the resources in the api |
yes I can, but I think due to your last comment I found the issue: API_URL is empty
https://github.com/tektoncd/hub/blob/main/docs/DEPLOYMENT.md#update-ui-configmap |
If you are installing Hub on openshift in that case the And if in case you are using it on other k8s cluster then for that we might have to add a support for that where you can provide the url and UI will be served on that url |
As of today you can add these fields only in the Hub CR https://github.com/tektoncd/operator/blob/main/docs/TektonHub.md |
I use OKD with the original tekton operator, because the tekton operator for openshift is not available on okd. so i think thats why its not working, i also have to manually create the ingress for UI and API
i can't see where i can configure there the URL, do you mean i can write the API_URL into the db secret? |
What I meant was as of today it is not supported to add the API_URL |
Should we open a Bug ticket for this? Because as I see this, without this set, the hub cr is basically unuseable. We could also think about automatically creating the ingress for API and UI so the API_URL could then be set based on the created ingress |
Yeah, that makes sense, would you mind to create another issue for that |
I am also running into this issue when trying to clone a repository using a ssh key.
Do not get misdirected by the output claiming to check your access rights. The error seems to be triggered by the missing uid in the image, causing ssh to exit abnormally. ConclusionI am suspecting that the missing uid SolutionOne of the two
EditI just confirmed this issue by u0-execing into the container, creating a user with the missing uid and successfully pulling the repository in |
Expected Behavior
Creates a working Tektonhub with the default tekton catalog
Actual Behavior
Fails with cloning the default tekton catalog repo
Steps to Reproduce the Problem
kubectl apply -f tektonhub.yml
this will create the following configmap
which will result in the following error
Additional Info
Kubernetes version:
Output of
kubectl version
:Tekton Pipeline version:
v0.53.3
Tekton Operator version:
v0.69.1
installed via OLM and operatorhub
The text was updated successfully, but these errors were encountered: