[YSQL] When release binaries are pulled, improve discoverability of what happened

[StachuDotNet]

Jira Link: DB-9853

Description

We install yugabyte in a dockerfile, and cURL the binaries as part of that process e.g. with https://downloads.yugabyte.com/releases/$YUGABYTE_VERSION/yugabyte-$YUGABYTE_VERSION-$YUGABYTE_BUILD-el8-aarch64.tar.gz.

Mysteriously, it broke recently. After some digging, I saw that we got a 403 when curling the zip.

My best guess is that, per #20648, the binaries we were referencing have been pulled from availability as there was a notable bug. Specifically, we were referencing 2.20.0.0 build b76, resolving to https://downloads.yugabyte.com/releases/2.20.0.0/yugabyte-2.20.0.0-b76-linux-x86_64.tar.gz. We've since updated what version we reference, and are fine.

My feedback here is that it would have been nice if the error was something other than a 403 - maybe a 410 Gone, or some extra text to indicate the issue.

Thanks for considering!

Issue Type

kind/improve-ux

Warning: Please confirm that this issue does not contain any sensitive information

• I confirm this issue does not contain any sensitive information.

[ddorian]

I don't think it's possible to set in S3 to return 410 error code.

[StachuDotNet]

I don't think it's possible to set in S3 to return 410 error code.

Maybe not - it just took me a while last night to figure out what was going on, so hoping for some way to prevent others from having to deal with the same.