You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The source-controller is unable to clone the repository and its submodules. It returns the following error during each attempt: failed to checkout and determine revision: unable to clone '<repository_url>': entry not found.
We are using a Github repository that uses submodules. We use the HTTP URL of the repository for cloning the repository. We tried using both Github app installation tokens and personal access tokens for the referenced secret but it still fails with the same error message.
We can clone the repository and its submodules manually without any problems using the same Github app installation token or personal access tokens. We also haven't encountered this issue when using a repository that does not use submodules even while using the same referenced secret (Github app installation token or personal access token).
Please refer to the additional context section for the details of our GitRepository resource and some logs from the source-controller.
Steps to reproduce
Prepare a repository that uses submodules.
Use something like flux create secret git and set a Github app installation token or personal access token for cloning the repository.
Use something like flux create source git to reference the repository that uses submodules.
Describe the bug
The source-controller is unable to clone the repository and its submodules. It returns the following error during each attempt:
failed to checkout and determine revision: unable to clone '<repository_url>': entry not found
.We are using a Github repository that uses submodules. We use the HTTP URL of the repository for cloning the repository. We tried using both Github app installation tokens and personal access tokens for the referenced secret but it still fails with the same error message.
We can clone the repository and its submodules manually without any problems using the same Github app installation token or personal access tokens. We also haven't encountered this issue when using a repository that does not use submodules even while using the same referenced secret (Github app installation token or personal access token).
Please refer to the additional context section for the details of our GitRepository resource and some logs from the source-controller.
Steps to reproduce
Expected behavior
Flux source controller is able to clone the repository along with its submodules.
Screenshots and recordings
No response
OS / Distro
Ubuntu 22.04
Flux version
v2.2.2
Flux check
► checking prerequisites
✔ Kubernetes 1.28.4-eks-8cb36c9 >=1.26.0-0
► checking version in cluster
✔ distribution: flux-v2.2.2
✔ bootstrapped: false
► checking controllers
✔ helm-controller: deployment ready
► ghcr.io/fluxcd/helm-controller:v0.37.2
✔ kustomize-controller: deployment ready
► ghcr.io/fluxcd/kustomize-controller:v1.2.1
✔ notification-controller: deployment ready
► ghcr.io/fluxcd/notification-controller:v1.2.3
✔ source-controller: deployment ready
► ghcr.io/fluxcd/source-controller:v1.2.3
► checking crds
✔ alerts.notification.toolkit.fluxcd.io/v1beta3
✔ buckets.source.toolkit.fluxcd.io/v1beta2
✔ gitrepositories.source.toolkit.fluxcd.io/v1
✔ helmcharts.source.toolkit.fluxcd.io/v1beta2
✔ helmreleases.helm.toolkit.fluxcd.io/v2beta2
✔ helmrepositories.source.toolkit.fluxcd.io/v1beta2
✔ kustomizations.kustomize.toolkit.fluxcd.io/v1
✔ ocirepositories.source.toolkit.fluxcd.io/v1beta2
✔ providers.notification.toolkit.fluxcd.io/v1beta3
✔ receivers.notification.toolkit.fluxcd.io/v1
✔ all checks passed
Git provider
Github
Container Registry provider
No response
Additional context
Our git repository resource:
Some logs from the source-controller (from start-up to recurring error message):
Code of Conduct
The text was updated successfully, but these errors were encountered: