khushalchandak17

I was able to replicate the issue by setting the token expiry to 10 minutes as shared by @m-ildefons. The Rancher deployed is v2.8.3, and the Harvester version is v1.2.1....

+1 I had seen similar behavior when we provide a invalid path in git-repo. Well, I have created a few scenarios to elaborate this issue in detail; Scenario 1: gitrepo...