Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Delete environment lock fails with timeout #2146

Open
ManuelRosa opened this issue Nov 28, 2024 · 1 comment
Open

Delete environment lock fails with timeout #2146

ManuelRosa opened this issue Nov 28, 2024 · 1 comment

Comments

@ManuelRosa
Copy link

We started to see our release train pipelines fail (after the "Trigger release train" step) because they cannot unlock all our environments for qa stage (there is a timeout)

If we try to do this for all environments in the UI we also get the same timeout.

Workaround: We manage to workaround this by removing the lock for a subset of environments instead of for all (30)
Impact: We cannot promote new versions unless we unlock the environment manually.

> DELETE /environment-groups/qa/locks/release-train-to-production-pilot HTTP/2
> Host: kuberpult.int.wawi.lidl
> user-agent: curl/7.81.0
> accept: */*
> content-type: application/json
> content-length: 832

...

100   832    0     0    0   832      0      0 --:--:--  0:14:58 --:--:--     0
100   832    0     0    0   832      0      0 --:--:--  0:14:59 --:--:--     0* TLSv1.2 (IN), TLS header, Supplemental data (23):
{ [5 bytes data]
< HTTP/2 504 
< date: Tue, 26 Nov 2024 14:53:39 GMT
< content-type: text/html
< content-length: 160
< strict-transport-security: max-age=31536000; includeSubDomains
< 
{ [160 bytes data]

100   992    0   160    0   832      0      0 --:--:--  0:15:00 --:--:--    34
* Connection #0 to host kuberpult.int.wawi.lidl left intact
curl: (22) The requested URL returned error: 504
<html>
<head><title>504 Gateway Time-out</title></head>
<body>
<center><h1>504 Gateway Time-out</h1></center>
<hr><center>nginx</center>
</body>
</html>
@ManuelRosa
Copy link
Author

We see the issue again today. This time it was more sever because we actually received a tiemout in the "Trigger release train" step for one of our production clusters. This prevented the automated deploymented to production.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ManuelRosa