-
Notifications
You must be signed in to change notification settings - Fork 14
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
Issues with Artifact Upload in Mender 3.7.4 #120
Comments
Hello @mehta-akshay-scanomat , are you using the official Helm Chart? Did you configure Azure Blob Storage as documented? Which Ingress controller are you using? |
|
It could be an Ingress controller timeout; with this troubleshooting tip, the solution was to increase the proxy body size. Maybe something similar also with Traefik. |
@oldgiova I tried to upload using mender-cli as well and got the 499 error as shown below:
When I used curl to upload artifact, I got the following response:
These are how my Traefik deployment and mender-deployment looks like
|
Hello @mehta-akshay-scanomat 👋 Hmm... Status code 499 is not a code a client should be able to receive 🤔 kubectl logs deploy/mender-deployments |
Hi @alfrunes,
I got only this thing in the logs of mender-deployments |
Thank you for sharing the logs, so the status code did not change after adjusting the ingress timeouts. Important Make sure you redact all sensitive information such as IP addresses and email addresses before posting here. |
Thank you @alfrunes for your reply. I was very hopeful that adjusting ingress timeouts will work but no luck. It's still showing same error as still getting timeout after one minute. Below are the logs of ingress and mender-api-gateway respectively:
|
Hello @mehta-akshay-scanomat . Could you give some more details about your setup?
Thanks |
Hi @oldgiova, here are the details you asked for:
|
Inspecting the logs, it seems like the connection between the |
Description:
I am currently using the open-source version of Mender (3.7.4) and encountering persistent issues when attempting to upload artifacts. Specifically, I receive a 5xx error during the upload process.
When using the UI to upload an artifact, I see the message: "Artifact couldn't be generated. Request failed with status code 502." The logs for the
mender-deployment
service show a corresponding status code of 500:When using
curl
, I receive a 502 Bad Gateway error:Using the Mender CLI for artifact uploads results in a status code 409.
I have identified a pattern: files that take longer than one minute to upload consistently fail, whereas smaller files (around 200-300 MB) that upload in under a minute succeed with a status code of 201.
Questions:
However, the issue persists. Any guidance on resolving this would be greatly appreciated!
Thank you!
The text was updated successfully, but these errors were encountered: