-
Feature
-
Resolution: Done-Errata
-
Normal
-
1.2
-
8
-
False
-
False
-
-
GITOPS Sprint 242
1. OpenShift-Gitops authentication issue tfs ( Microsoft Team Foundation Server) type git repos Configured via custom resource and secret containing user id and token. while trying to authenticate facing the below error:
~~~
Unable to create application: application spec is invalid: InvalidSpecError: Unable to get app details: rpc error: code = Internal desc = Failed to fetch: `git fetch origin --tags --force` failed exit status 128: fatal: Authentication failed for 'https://tfs.URL:15443/tfs//_git/openshift-URL/
~~~
ArgoCD seems to be able to connect to the repository as the GUI shows it as connected ( connection status Successful)
2. It is strange to us as it seems that Argocd is able to get the latest commit, but is unable to pull it from tfs.
Also there are open issues in ArgoCD Github with the same use cases and errors.
https://github.com/argoproj/argo-cd/issues/6289
Azure TFS is in prem and is Version Dev18.M170.8 same as the above issue.
3. List of affected packages or components.
ArgoCD
GitOps Operator
Auth
Findings: TFS not included in https://argoproj.github.io/argo-cd/user-guide/private-repositories/#access-token
Acceptance Criteria:
- Create tests for TFS and Azure Git repositories
- Make sure the right exchange keys are used (please update the known-hosts information in the defaults.go file of the argocd-operator)
- We are using the right version of git which is greater than >=2.34 (dependency on the UBI image)
- is blocked by
-
GITOPS-2768 Outdated Git version in downstream image
- Closed
- relates to
-
GITOPS-2768 Outdated Git version in downstream image
- Closed
-
ACM-3880 Add support for Azure DevOps repositories in ACM
- Closed