-
Notifications
You must be signed in to change notification settings - Fork 5.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
test: wait longer after repo server restarted to avoid errors on s390x #12839
Conversation
Signed-off-by: Sam Ding <samding@ca.ibm.com>
@@ -811,6 +811,8 @@ func RestartRepoServer() { | |||
} | |||
FailOnErr(Run("", "kubectl", "rollout", "restart", "deployment", workload)) | |||
FailOnErr(Run("", "kubectl", "rollout", "status", "deployment", workload)) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The rollout status
should already wait until a workload is available. I think we should really avoid using introducing newSleep
calls with a fixed time length.
Why is this only needed on s390x?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See http://pastebin.test.redhat.com/1094074
for failed cases log, on s390x the rollout status
does not wait enough longer, and causes the follow calling to argocd repo server failed
/cherry-pick release-2.4 |
/cherry-pick release-2.5 |
/cherry-pick release-2.6 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
#12839) Signed-off-by: Sam Ding <samding@ca.ibm.com>
#12839) Signed-off-by: Sam Ding <samding@ca.ibm.com>
#12839) Signed-off-by: Sam Ding <samding@ca.ibm.com>
argoproj#12839) Signed-off-by: Sam Ding <samding@ca.ibm.com>
argoproj#12839) Signed-off-by: Sam Ding <samding@ca.ibm.com>
Add a wait time 10 seconds after
repo server
is restarted to avoidconnection refused
error on s380xin the following 7 cases: