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.

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

504 Gateway Time-out when we want to GET link after the draft export airlock request is created #3240

Closed
dusan-ilic-mhra opened this issue Feb 22, 2023 · 8 comments
Labels
bug Something isn't working

Comments

@dusan-ilic-mhra
Copy link
Contributor

Describe the bug
In version v0.7.0 which is currently on our DEV environment, we get 504 Gateway Time-out every time when we:

  1. create a draft export airlock request:
    image

  2. GET/api/workspaces/{workspace_id}/requests/{airlock_request_id}/link:
    image

  3. And, this is the log from App Service:
    image

  4. After that, the environment is unavailable for a while with 502 and 504 gateway errors.

Steps to reproduce

Explained above.

@dusan-ilic-mhra dusan-ilic-mhra added the bug Something isn't working label Feb 22, 2023
@dusan-ilic-mhra
Copy link
Contributor Author

Hello @tamirkamara, @marrobi

This is a blocker for us currently.
Could you please help us to resolve this issue?

@dusan-ilic-mhra
Copy link
Contributor Author

@tamirkamara, @marrobi

For the import airlock requests we are getting the link, this issue is happening only when we want to do an export.

@dusan-ilic-mhra
Copy link
Contributor Author

dusan-ilic-mhra commented Feb 23, 2023

@tamirkamara, @marrobi

After digging more into app service logs we can see that connection to the airlock export storage account within the workspace is timing out:

image

You can see the full log here:

connection-timeout-storage-account-stalexintws99b6.txt

Could you pelase advise?

@marrobi
Copy link
Member

marrobi commented Feb 23, 2023

I believe this has been fixed in a more recent update -#3215

Sometimes the private link DNS records were not being created correctly.

@tamirkamara think this is the same issue?

@migldasilva
Copy link
Contributor

@tamirkamara We have just applied the changes proposed by @marrobi in this comment.

However we still have the timeout problem.

I uploaded the full log in this comment.
Log_Default_Docker.txt

@marrobi
Copy link
Member

marrobi commented Jan 9, 2024

@migldasilva do you still hit this? It was resolved, and required changes detailed in the release notes. Thanks.

@migldasilva
Copy link
Contributor

@marrobi We haven't noticed this issue for a while. Thanks for the clarification, I'll review the release notes.

@marrobi
Copy link
Member

marrobi commented Jan 11, 2024

OK, I'll close the issue, if you see it again, let us know.

@marrobi marrobi closed this as completed Jan 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants