Bug: Git sensor got error and return exit code 128

[tommy04062019]

📜 Description

Logs:
│ git-sensor {"level":"info","ts":1723014048.660751,"caller":"pkg/RepoManages.go:468","msg":"errored material ","id":4,"errMsg":"exit status 128"} │ │ git-sensor {"level":"error","ts":1723014050.2870855,"caller":"git/GitBaseManager.go:185","msg":"error in git cli operation","msg":"fatal: not a git repository (or any of the parent directories): .git\ │ │ git-sensor {"level":"error","ts":1723014050.2873294,"caller":"git/RepositoryManager.go:204","msg":"error in updating repository","err":"exit status 128","location":"git@xxxx │ │ git-sensor {"level":"error","ts":1723014050.287529,"caller":"git/Watcher.go:200","msg":"error in fetching material details ","repo":"git@xxxxxxxx","err":"exit s │ │ git-sensor {"level":"error","ts":1723014050.2898335,"caller":"git/GitBaseManager.go:185","msg":"error in git cli operation","msg":"fatal: not in a git directory\n","err":"exit status 128","stacktrace" │ │ git-sensor {"level":"error","ts":1723014050.2899919,"caller":"git/RepositoryManager.go:367","msg":"error in configuring ssh command while adding repo","errorMsg":"","err":"exit status 128","stacktrace │ │ git-sensor {"level":"error","ts":1723014050.2901144,"caller":"git/Watcher.go:212","msg":"error in creating/configuring ssh private key on disk ","repo":"git@xxxxxx │ │ git-sensor {"level":"info","ts":1723014050.4152596,"caller":"pkg/RepoManages.go:468","msg":"errored material ","id":4,"errMsg":"exit status 128"}

👟 Reproduction steps

When I run Build and Deploy. Got an error:

👍 Expected behavior

Pulling code should successfully

👎 Actual Behavior

Return code 128

☸ Kubernetes version

1.28

Cloud provider

openstack

🌍 Browser

Chrome

🧱 Your Environment

No response

✅ Proposed Solution

No response

👀 Have you spent some time to check if this issue has been raised before?

• I checked and didn't find any similar issue

🏢 Have you read the Code of Conduct?

• I have read the Code of Conduct

[ayu-devtron]

Hi @tommy04062019 , If you are still facing this issue then can you please tell us steps to reproduce this ? Also, if its possible then can you tell us the repo for which this happened ?

[ayu-devtron]

Hi @tommy04062019 , we believe this error happened because either you didn't have proper access to the target repo or repo url was incorrect. Either way, we have done improvements on our side to show meaningful error messages on UI.

I am closing this issue for now but feel free to open this if you feel otherwise.