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
when I tried to deploy the application it was deploying with no error, but it was stuck in argocd sync for more than 1 hour and the changes were not reflected in the Argo dashboard it was showing no diff ,
after that, I clone that gitops repo and check the commits, looks like the commits are not there for new deployment
When I check in db it's showing a new gitops repo .
Affected areas
CD
Additional affected areas
None
Prod/Non-prod environments?
Prod
Is User unblocked?
Yes
How was the user un-blocked?
PERMANENTLY - By giving a workaround (Within Devtron)
Impact on Enterprise
Not able to deploy there prod application .
👟 Steps to replicate the Issue
NA
👍 Expected behavior
It should work fine
👎 Actual Behavior
It is not working fine
☸ Kubernetes version
1.25
Cloud provider
aws
🌍 Browser
Chrome
✅ Proposed Solution
No response
👀 Have you spent some time to check if this issue has been raised before?
📜 Description
when I tried to deploy the application it was deploying with no error, but it was stuck in argocd sync for more than 1 hour and the changes were not reflected in the Argo dashboard it was showing no diff ,
after that, I clone that gitops repo and check the commits, looks like the commits are not there for new deployment
When I check in db it's showing a new gitops repo .
Affected areas
CD
Additional affected areas
None
Prod/Non-prod environments?
Prod
Is User unblocked?
Yes
How was the user un-blocked?
PERMANENTLY - By giving a workaround (Within Devtron)
Impact on Enterprise
Not able to deploy there prod application .
👟 Steps to replicate the Issue
NA
👍 Expected behavior
It should work fine
👎 Actual Behavior
It is not working fine
☸ Kubernetes version
1.25
Cloud provider
🌍 Browser
Chrome
✅ Proposed Solution
No response
👀 Have you spent some time to check if this issue has been raised before?
🏢 Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: