'mender-cli artifacts upload' fails occasionally with status 502 - bad gateway

Hello all,

uploading mender artifacts using ‘mender-cli artifacts upload’ occasionally fails with the following error:

FAILURE: artifact upload failed with status 502, reason: Bad Gateway

This started a few weeks ago but I don’t remember when. Didn’t report this immediately because I thought it was a temporary glitch, but want to make you aware of this now. Last time this occured was today 15:26:01 CEST. Usually I just restart the CI job and next time it succeeds.

Regards,
Manuel

Hello all,

we’re still facing these issues. In the meantime, the Bad Gateway string got encapsulated into HTML.

FAILURE: artifact upload failed with status 502, reason: <html>
<head><title>502 Bad Gateway</title></head>
<body>
<center><h1>502 Bad Gateway</h1></center>
</body>
</html>

Today this occured at 14:17:52 and 14:31:37 CET (= UTC+1).

Hello,

can provide some statistics from yesterday 2021-11-24. All times are in CET = UTC+1.

14:17:52 -- upload failed with http 502 bad gateway
14:31:37 -- upload failed with http 502 bad gateway
14:58:26 -- upload successful
15:03:17 -- upload successful
15:22:06 -- upload successful
15:25:19 -- upload failed with http 502 bad gateway
18:56:14 -- upload successful
19:01:08 -- upload successful

Our CI job is signing in with mender-cli login --server "https://hosted.mender.io" --username username --password password and uploading with mender-cli artifacts upload --no-progress <artifact-path>. For context, we also get a Configuration file not found. Continuing., but that shouldn’t be related to the problem on hand, I guess.

What can cause such an http 502 error?

My gut feeling based on the logs is that most likely it’s something with network in the CI system. As long as all required options are provided via command line parameters Configuration file not found. Continuing. message can be ignored. The only thing, which attracts my attention, is missing --server parameter in mender-cli artifacts upload --no-progress <artifact-path>, but upload successful message indicates that it’s somehow configured.

Hi guys.
Is this issue maybe resolved somehow?
I have an artifact of size 6.5GB and am trying now for the 8th or 9th time to upload the artifact to the server using CLI and GUI. Each time I get status 502. Sometimes on 50%, sometimes 70%. There is no pattern in failure and there is no message of an upload limit.
Thanks.

I didn’t observe this issue for quite some time now.