Description of problem: For a while we have been using metalink urls in Fedora for doing kickstarts as shown here in the fedora 25 branch of the kickstarts repo: https://pagure.io/fedora-kickstarts/blob/9eb21cb2b921255102e6e6eff8219a4e19b55cca/f/fedora-repo-not-rawhide.ks In fedora 26 this stopped working. In fedora 26 if I change a url from repo --name=fedora --mirrorlist=https://mirrors.fedoraproject.org/metalink?repo=fedora-$releasever&arch=$basearch to repo --name=fedora --mirrorlist=https://mirrors.fedoraproject.org/mirrorlist?repo=fedora-$releasever&arch=$basearch then it works. Is this a bug or should this has never worked before? Version-Release number of selected component (if applicable): 15:04:18,849 INFO anaconda:/sbin/anaconda 26.21.3-1 How reproducible: Always Steps to Reproduce: 1. do a kickstart with https://kojipkgs.fedoraproject.org/compose/branched/Fedora-26-20170430.n.0/compose/Everything/x86_64/iso/Fedora-Everything-netinst-x86_64-26-20170430.n.0.iso 2. specify a kickstart like: https://kojipkgs.fedoraproject.org//work/tasks/2790/19322790/koji-f26-build-19322790-base.ks Actual results: 15:04:21,676 INFO packaging:Trying to download '.treeinfo' 15:04:21,680 INFO packaging:Server returned 404 code 15:04:21,680 INFO packaging:Trying to download 'treeinfo' 15:04:21,681 INFO packaging:Server returned 404 code 15:04:21,681 ERR packaging:Got HTTP 404 Error when downloading [.]treeinfo files and an interactive screen asking you to specify where to install software from Expected results: Additional info:
Can you attach the logs from the failed install (find 'em in /tmp , in the installation environment)? Hopefully they'll give us more clues as to what's going on.
Created attachment 1277963 [details] anaconda logs
Created attachment 1277965 [details] anaconda.log (extracted from tarball)
Created attachment 1277966 [details] dnf.librepo.log (extracted from tarball)
Created attachment 1277967 [details] hawkey.log (extracted from tarball)
Created attachment 1277968 [details] packaging.log (extracted from tarball)
Created attachment 1277969 [details] program.log (extracted from tarball)
Created attachment 1277970 [details] syslog (extracted from tarball)
Created attachment 1278542 [details] kickstart from f25 install confirmed that this used to work in f25 by starting an install from the url http://download.fedoraproject.org/pub/fedora/linux/releases/25/Everything/x86_64/os/ and using the attached kickstart file
Since we don't know when this broke, I'm going to assume it's been broken since the beginning of Fedora 26. That said, there are two potential places it could have broken: * Anaconda's dnfpayload module: https://github.com/rhinstaller/anaconda/commits/f26-devel/pyanaconda/payload/dnfpayload.py ** Mirrorlist handling logic: https://github.com/rhinstaller/anaconda/blob/f26-devel/pyanaconda/payload/dnfpayload.py#L348 * DNF's repo module: https://github.com/rpm-software-management/dnf/commits/master/dnf/repo.py ** Mirrorlist handling logic: https://github.com/rpm-software-management/dnf/blob/master/dnf/repo.py#L693 I don't see any particularly obvious reason it should be broken, as the logic is supposed to evaluate whether it's a metalink and then use it that way. That particular section of the code hasn't changed all that much in years, except for one thing: https://github.com/rpm-software-management/dnf/commit/9809b1648847ca2cf1ae47914303a63e043d78b7 And that particular change shouldn't have broken anything. If anything, it should have fixed some issues...
On further thought, it's also possible that librepo is where this is broken, due to the change introduced to select the correct repo URL type. If that's the case, then this is likely a bug in librepo, rather than Anaconda or DNF.
*** Bug 1451040 has been marked as a duplicate of this bug. ***
Yes since updating to F26 (all was ok on 25) I have not been able to use livecd-creator as it does not fine the repos. Yet dnf works fine on the command line. Same issue with livemedia creator.
As comment #13 says, livecd-creator also doesn't work with the metalinks anymore. It looks like the error is at a deeper layer, unless we have 2 separate bugs.
Still not working on Rawhide F29.
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '26'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
This bug appears to have been reported against 'rawhide' during the Fedora 29 development cycle. Changing version to '29'.
In Fedora 29 neither mirrorlist nor baseurl work either. With mirrorlist: bkelly ~ livecd ci-spin cat fedora-repo-not-rawhide.ks repo --name=fedora --mirrorlist=https://mirrors.fedoraproject.org/mirrorlist?repo=fedora-$releasever&arch=$basearch repo --name=updates --mirrorlist=https://mirrors.fedoraproject.org/mirrorlist?repo=updates-released-f$releasever&arch=$basearch repo --name=updates-testing --mirrorlist=https://mirrors.fedoraproject.org/mirrorlist?repo=updates-testing-f$releasever&arch=$basearch url --mirrorlist=https://mirrors.fedoraproject.org/mirrorlist?repo=fedora-$releasever&arch=$basearch Mounting /dev/loop0 at /var/tmp/imgcreate-pnvq9hux/install_root Skipping (/sys/fs/selinux,/sys/fs/selinux) because source doesn't exist. fedora 16 kB/s | 46 kB 00:02 updates 16 kB/s | 46 kB 00:02 updates-testing 16 kB/s | 46 kB 00:02 Failed to synchronize cache for repo 'fedora', ignoring this repo. Failed to synchronize cache for repo 'updates', ignoring this repo. Failed to synchronize cache for repo 'updates-testing', ignoring this repo. Error creating Live CD : Failed to find group 'core' : no such group Unmounting directory /var/tmp/imgcreate-pnvq9hux/install_root Losetup remove /dev/loop0 With baseurl: bkelly ~ livecd hotspot-spin cat fedora-repo-not-rawhide.ks repo --name=fedora --mirrorlist=https://mirrors.fedoraproject.org/mirrorlist?repo=fedora-$releasever&arch=$basearch repo --name=updates --mirrorlist=https://mirrors.fedoraproject.org/mirrorlist?repo=updates-released-f$releasever&arch=$basearch #repo --name=updates-testing --mirrorlist=https://mirrors.fedoraproject.org/mirrorlist?repo=updates-testing-f$releasever&arch=$basearch repo --name=updates-testing baseurl=http://ftp.saix.net/linux/distributions/fedora/linux/updates/testing/$releasever/Everything/$basearch/ url --mirrorlist=https://mirrors.fedoraproject.org/mirrorlist?repo=fedora-$releasever&arch=$basearch bkelly ~ livecd hotspot-spin spinit.sh ~/livecd/fedora-kickstarts ~/livecd/hotspot-spin M fedora-repo-not-rawhide.ks Already on 'f29' Your branch is up to date with 'origin/f29'. From https://pagure.io/fedora-kickstarts * branch f29 -> FETCH_HEAD Already up to date. ~/livecd/hotspot-spin ~/livecd/common ~/livecd/hotspot-spin M extrarepos.ks Already on 'f29' ~/livecd/hotspot-spin Using title 'Hotspot Spin' and product 'Hotspot Spin' kickstart error: Failed to parse kickstart file 'file:///home/bkelly/livecd/hotspot-spin/hotspot-spin.ks' : The following problem occurred on line 4 of the kickstart file: unrecognized arguments: baseurl=http://ftp.saix.net/linux/distributions/fedora/linux/updates/testing/$releasever/Everything/$basearch/
This message is a reminder that Fedora 29 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '29'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 29 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
anyone know where we are with this ATM?
I think this should be closed. We have --metalink from Fedora 27 which should be used instead of mirrorlist for metalinks. There were also some changes to accept metalinks more appropriately in the --mirrorlist because of backward compatibility with yum, so it may be already fixed even from that side. So or so, using --mirrorlist for metalinks is discouraged. https://pykickstart.readthedocs.io/en/latest/kickstart-docs.html#repo
Yeah I'm not sure. I trust @jkonecny
Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.