tickets #112208
openopenSUSE-Leap-15.4-DVD-x86_64-Media.iso redirected to openSUSE-Leap-15.4-DVD-x86_64-Build243.2-Media.iso
0%
Description
I don't know if this is actually an issue :-)
wget -nd http://download.opensuse.org/distribution/leap/15.4/iso/openSUSE-Leap-15.4-DVD-x86_64-Media.iso
--2022-06-08 16:19:17-- http://download.opensuse.org/distribution/leap/15.4/iso/openSUSE-Leap-15.4-DVD-x86_64-Media.iso
Resolving download.opensuse.org (download.opensuse.org)... 195.135.221.134, 2001:67c:2178:8::13
Connecting to download.opensuse.org (download.opensuse.org)|195.135.221.134|:80... connected.
HTTP request sent, awaiting response... 302 Found
Location: /distribution/leap/15.4/iso/openSUSE-Leap-15.4-DVD-x86_64-Build243.2-Media.iso [following]
--2022-06-08 16:19:17-- http://download.opensuse.org/distribution/leap/15.4/iso/openSUSE-Leap-15.4-DVD-x86_64-Build243.2-Media.iso
Reusing existing connection to download.opensuse.org:80.
HTTP request sent, awaiting response... 302 Found
Location: http://mirrorcache-eu.opensuse.org/distribution/leap/15.4/iso/openSUSE-Leap-15.4-DVD-x86_64-Build243.2-Media.iso [following]
URL transformed to HTTPS due to an HSTS policy
--2022-06-08 16:19:17-- https://mirrorcache-eu.opensuse.org/distribution/leap/15.4/iso/openSUSE-Leap-15.4-DVD-x86_64-Build243.2-Media.iso
Resolving mirrorcache-eu.opensuse.org (mirrorcache-eu.opensuse.org)... 195.135.221.140, 2001:67c:2178:8::16
Connecting to mirrorcache-eu.opensuse.org (mirrorcache-eu.opensuse.org)|195.135.221.140|:443... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://opensusemirror.lihaso.com//distribution/leap/15.4/iso/openSUSE-Leap-15.4-DVD-x86_64-Build243.2-Media.iso [following]
--2022-06-08 16:19:17-- https://opensusemirror.lihaso.com//distribution/leap/15.4/iso/openSUSE-Leap-15.4-DVD-x86_64-Build243.2-Media.iso
Resolving opensusemirror.lihaso.com (opensusemirror.lihaso.com)... 46.140.178.124
Connecting to opensusemirror.lihaso.com (opensusemirror.lihaso.com)|46.140.178.124|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 4083154944 (3.8G) [application/x-iso9660-image]
Saving to: ‘openSUSE-Leap-15.4-DVD-x86_64-Media.iso’
Should download.o.o really be giving me the symlink target Location: /distribution/leap/15.4/iso/openSUSE-Leap-15.4-DVD-x86_64-Build243.2-Media.iso
?
There was already a question on the users list about the same - the iso was downloaded as openSUSE-Leap-15.4-DVD-x86_64-Build243.2-Media.iso
, so when the user tried "sha256sum -c openSUSE-Leap-15.4-DVD-x86_64-Media.iso.sha256", it didn't work, file not found.
Updated by pjessen over 2 years ago
- Subject changed from openSUSE-Leap-15.4-DVD-x86_64-Media.iso symlinked to openSUSE-Leap-15.4-DVD-x86_64-Build243.2-Media.iso to openSUSE-Leap-15.4-DVD-x86_64-Media.iso redirected to openSUSE-Leap-15.4-DVD-x86_64-Build243.2-Media.iso
Updated by pjessen over 2 years ago
I'm still not sure to which extent this is a real issue, but it does seem to be problematic when people download the checksum file, but are then unable to check it using the standard method. Also, although download.o.o is clearly not "just another mirror", wrt filenames should it not behave the same as other mirrors?
Updated by crameleon about 1 year ago
- Assignee set to opensuse-admin-obs
Machine is no longer maintained by openSUSE Heroes, re-assigning to Build team.
Updated by andriinikitin about 2 months ago
- Assignee changed from opensuse-admin-obs to andriinikitin
Updated by andriinikitin about 2 months ago
- Status changed from New to Workable
- Assignee changed from andriinikitin to lkocman
Hi,
This is tricky because internally openSUSE-Leap-15.4-DVD-x86_64-Media.iso is a symlink to a particular file, e.g. currently openSUSE-Leap-15.4-DVD-x86_64-Build243.2-Media.iso
However, theoretically, the destination can change at any moment, which might create confusion during troubleshooting. (Well, maybe not for 15.4 anymore, but it is still the case for 15.5 and 15.6.)
Moreover, download.opensuse.org doesn't usually serve files directly but tries to redirect a mirror closest to the request origin. On that mirror, the symlink might point to, e.g., an old Build, which might create even more confusion.
Thus it is much more transparent if the request is redirected to a particular Build, and further, it is redirected to a mirror, which has that exact Build.
Now the valid question is what should be inside the .sha256 file. There is no silver bullet because the server doesn't know which name will be chosen by the client program. For E.g. in your example, wget saves the file without Build, so the checksum program should succeed.
If the client program really chooses destination name from redirect (e.g. flag --content-disposition for wget), then it is better to use it with Current
suffix instead of Media
, e.g. openSUSE-Leap-15.4-DVD-x86_64-Current.iso.sha256 . It will redirect to the file which contains the name with Build, e.g.
> wget --content-disposition http://download.opensuse.org/distribution/leap/15.4/iso/openSUSE-Leap-15.4-DVD-x86_64-Current.iso.sha256
...
2024-10-24 15:53:45 (21.2 MB/s) - ‘openSUSE-Leap-15.4-DVD-x86_64-Build243.2-Media.iso.sha256’ saved [117/117]
> cat openSUSE-Leap-15.4-DVD-x86_64-Build243.2-Media.iso.sha256
4683345f242397c7fd7d89a50731a120ffd60a24460e21d2634e783b3c169695 openSUSE-Leap-15.4-DVD-x86_64-Build243.2-Media.iso
I agree that this is a bit cumbersome behavior, so will assign the ticket to the openSUSE Release Manager, so he defines how behavior should look when user requests to download these files:
openSUSE-Leap-15.4-DVD-x86_64-Media.iso : currently redirects to a mirror containing openSUSE-Leap-15.4-DVD-x86_64-Build243.2-Media.iso
openSUSE-Leap-15.4-DVD-x86_64-Media.iso.sha256 : currently renders file without Build in it (i.e. openSUSE-Leap-15.4-DVD-x86_64-Media.iso)
openSUSE-Leap-15.4-DVD-x86_64-Current.iso : currently redirects to a mirror containing openSUSE-Leap-15.4-DVD-x86_64-Build243.2-Media.iso
openSUSE-Leap-15.4-DVD-x86_64-Current.iso.sha256 : currently renders file with Build in it (i.e. openSUSE-Leap-15.4-DVD-x86_64-Build243.2-Media.iso)
Updated by andriinikitin about 2 months ago
- Related to tickets #95045: checksum failures - wrong name listed added
Updated by lkocman about 2 months ago
Let me tell you what is the problem
I need to get the latest published build any time when somebody clicks on download here https://get.opensuse.org/leap/15.6/
As of now we use -Media, There is also the -Current symlink which I'm not sure is really needed.
Downloadable's filename should match with content of the checksum files, which are signed (there is asc file).
In the past with GA we did request to rename files including the checksums files, but that is somehow problematic and manual effort.
Plus we refreshed images post GA with Quaterly Updates etc.
If somebody has better idea, which doesn't require any manual steps, let's do it.
Updated by andriinikitin about 2 months ago
- Assignee changed from lkocman to andriinikitin