https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# fleet
a
This message was deleted.
c
there is an issue with Fleet in Rancher 2.8+ & azure devops fix is in progress
t
Sounds lovely, any idea when it will be released or is it part of some beta that one can try?
c
there are certainly workarounds (replacing the fleet version in Rancher), not ready for production use though
Is it this issue ? https://github.com/rancher/fleet/issues/2043 your description looks a bit different actually
t
I have not seen this error message "Error cloning repository: empty git-upload-pack given" but then again I'm not sure where to look for logs regarding this...
Ok, I found an error message now: time="2024-02-26T114258Z" level=info msg="Starting to clone git repository" _Error: unexpected client error: unexpected requesting "https://dev.azure.com/BolidenDevOps/JawCrusher/_git/fleet-examples/git-upload-pack" status code: 400_ Usage: gitcloner [REPO] [PATH] [flags] Flags: -b, --branch string git branch --ca-bundle-file string CA bundle file -h, --help help for gitcloner --insecure-skip-tls do not verify tls certificates --known-hosts-file string known hosts file --password-file string password file for basic auth --revision string git revision --ssh-private-key-file string ssh private key file path -u, --username string user name for basic auth _time="2024-02-26T114259Z" level=error msg="Error cloning repository: unexpected client error: unexpected requesting \"https://dev.azure.com/BolidenDevOps/JawCrusher/_git/fleet-examples/git-upload-pack\" status code: 400"_
Would you happen to know how to get a hold of this version. So far we are just running the docker-version of rancher... Saw one workaround was to downgrade to fleet:102.2.1+up0.8.1 Which I did, and stuff started working, just to stop working within minutes. I saw that somehow it had reverted back to the newer version of fleet. 1. Can I run a newer rancher docker image with this feature implemented vurrently running 2.9-head? 2. How can I keep the version at 102.2.1?
c
which version of Rancher are you on?
t
I'm using the dockerimage 2.9-head
c
oh this is in development
play with it at your own risks
t
You mean 2.9-head is in development? But how to I get the fix for adding azure repos? Is it a different image? Or is there a configuration within Rancher?
c
yes 2.9-head is in development, you should use 2.8.2 and you can try to change the fleet version with an rc image of fleet
t
Sorry, new to Rancher. But how to I change the fleet version to a newer version? I assume it is somewhere here I should change something? Currently running fleet:103.1.0+up0.9.0. That is the latest I can select with current configuration. Do I have to update a repository to find other versions of fleet?
c
@tall-hydrogen-17043 If you can easily reinstall your cluster, you could try the version 2.8-head and update the main repository to use the branch dev-v2.8 instead of release-v2.8
The branch dev-v2.8 contains the latest Fleet rc
And then you can update Fleet to that RC
we are still working on head-2.9 but we haven't updated it with the latest Fleet version
dev-v2.8 contains Fleet 0.9.1-rc.5 that contain the azure devops fix
c
^^ this is to check if your issue is indeed fixed in coming release, not for production use
t
Thank you very much, it started working. There is one more question. How do I separate customer projects in fleet? Workspaces seem like a good start but there are problems with using it. For example, how do I copy clusters to the new workspace? And how do I avoid exposing the local rancher repo if giving access to a workspace?
c
You should take your question as a separate message in the channel to get more chances you'll get eyes on it
c
@tall-hydrogen-17043 You may look into https://fleet.rancher.io/multi-user Also from a Rancher perspective, we are currently working on better integrating Rancher RBAC and Fleet RBAC
Open in Slack
PreviousNext
Powered by