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
If you are trying to resolve an environment-specific issue or have a one-off question about the edge case that does not require a feature then please consider asking a question in argocd slack channel.
Describe the bug
It's related to argocd notifications but the errors are coming from argocd-repo-server
I'm unable to produce notifications using repo calls (like .repo.GetCommitMetadata e.g) - it worked a single time (and once only) and since then every other try ends with an error:
argocd-notifications-controller-7df6c975f5-qlcm7 argocd-notifications-controller time="2021-11-25T19:58:17Z" level=error msg="Failed to notify recipient {slack argocd-all-alerts} defined in resource argocd/argo-config: template: app-deployed:18:18: executing \"app-deployed\" at <call .repo.GetCommitMetadata .app.status.sync.revision>: error calling call: rpc error: code = Internal desc = Failed to fetch 54bbb5a4c68cabd9f5162179a5512edbb241affb: git fetch origin --tags --forcefailed exit status 128: Could not create directory '/home/argocd/.ssh' (Read-only file system).\r\nFailed to add the ECDSA host key for IP address '51.68.x.xx' to the list of known hosts (/home/argocd/.ssh/known_hosts).\r\[email protected]: Permission denied (publickey).\r\nfatal: Could not read from remote repository.\n\nPlease make sure you have the correct access rights\nand the repository exists." resource=argocd/argo-config
and cert are there which I can view by: argocd cert list --cert-type ssh
Before I did that (add certs) another error was present - about the host being not known. After certs were added I was able to successfully produce notification using .repo calls once (pic) and that's it - every other try ends with the above error.
Error in argocd repo server:
time="2021-11-26T13:28:08Z" level=info msg="revision metadata cache miss: [email protected]:iops/cloud-infrastructure/k8s-clusters-bootstrapping.git/97c4b66b499f975caaba899664f4699b892503a1"
time="2021-11-26T13:28:08Z" level=error msg="`git fetch origin --tags --force` failed exit status 128: Could not create directory '/home/argocd/.ssh' (Read-only file system).\r\nFailed to add the ECDSA host key for IP address '51.68.x.x' to the list of known hosts (/home/argocd/.ssh/known_hosts).\r\[email protected]: Permission denied (publickey).\r\nfatal: Could not read from remote repository.\n\nPlease make sure you have the correct access rights\nand the repository exists." execID=EUGnD
At the same time application sync is working correctly.
To Reproduce
try to use .repo.GetCommitMetadata call in argocd notifications
If you are trying to resolve an environment-specific issue or have a one-off question about the edge case that does not require a feature then please consider asking a question in argocd slack channel.
Checklist:
argocd version
.Describe the bug
It's related to argocd notifications but the errors are coming from argocd-repo-server
I'm unable to produce notifications using repo calls (like .repo.GetCommitMetadata e.g) - it worked a single time (and once only) and since then every other try ends with an error:
argocd-notifications-controller-7df6c975f5-qlcm7 argocd-notifications-controller time="2021-11-25T19:58:17Z" level=error msg="Failed to notify recipient {slack argocd-all-alerts} defined in resource argocd/argo-config: template: app-deployed:18:18: executing \"app-deployed\" at <call .repo.GetCommitMetadata .app.status.sync.revision>: error calling call: rpc error: code = Internal desc = Failed to fetch 54bbb5a4c68cabd9f5162179a5512edbb241affb: git fetch origin --tags --forcefailed exit status 128: Could not create directory '/home/argocd/.ssh' (Read-only file system).\r\nFailed to add the ECDSA host key for IP address '51.68.x.xx' to the list of known hosts (/home/argocd/.ssh/known_hosts).\r\[email protected]: Permission denied (publickey).\r\nfatal: Could not read from remote repository.\n\nPlease make sure you have the correct access rights\nand the repository exists." resource=argocd/argo-config
I've added our private gitlab instance ssh certs by:
ssh-keyscan gitlab.xxx.xxx.com | argocd cert add-ssh --batch
and cert are there which I can view by:
argocd cert list --cert-type ssh
Before I did that (add certs) another error was present - about the host being not known. After certs were added I was able to successfully produce notification using .repo calls once (pic) and that's it - every other try ends with the above error.
Error in argocd repo server:
At the same time application sync is working correctly.
To Reproduce
try to use
.repo.GetCommitMetadata
call in argocd notificationsExpected behaviour
Ability to use repo calls every time
The text was updated successfully, but these errors were encountered: