Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1879127
Summary: | a metalink repository can't be added using UI | ||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Kamil Páral <kparal> | ||||||||||||||||
Component: | anaconda | Assignee: | Vendula Poncova <vponcova> | ||||||||||||||||
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||||
Severity: | unspecified | Docs Contact: | |||||||||||||||||
Priority: | unspecified | ||||||||||||||||||
Version: | 33 | CC: | anaconda-maint-list, awilliam, bcotton, jkonecny, jonathan, kellin, mkolman, robatino, vanmeeuwen+fedora, vponcova, wwoods | ||||||||||||||||
Target Milestone: | --- | ||||||||||||||||||
Target Release: | --- | ||||||||||||||||||
Hardware: | Unspecified | ||||||||||||||||||
OS: | Unspecified | ||||||||||||||||||
Whiteboard: | AcceptedFreezeException AcceptedBlocker | ||||||||||||||||||
Fixed In Version: | anaconda-33.25.2-4 anaconda-33.25.2-4.fc33 anaconda-33.25.4-1.fc33 | Doc Type: | If docs needed, set a value | ||||||||||||||||
Doc Text: | Story Points: | --- | |||||||||||||||||
Clone Of: | Environment: | ||||||||||||||||||
Last Closed: | 2020-09-21 20:49:19 UTC | Type: | Bug | ||||||||||||||||
Regression: | --- | Mount Type: | --- | ||||||||||||||||
Documentation: | --- | CRM: | |||||||||||||||||
Verified Versions: | Category: | --- | |||||||||||||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||||||
Embargoed: | |||||||||||||||||||
Bug Depends On: | |||||||||||||||||||
Bug Blocks: | 1766776, 1766777 | ||||||||||||||||||
Attachments: |
|
Description
Kamil Páral
2020-09-15 13:47:32 UTC
Created attachment 1714932 [details]
repo definition
Created attachment 1714933 [details]
error in the main hub
Created attachment 1714934 [details]
anaconda.log
Created attachment 1714935 [details]
dnf.librepo.log
Created attachment 1714936 [details]
packaging.log
Created attachment 1714937 [details]
program.log
Created attachment 1714938 [details]
syslog
I'm proposing this as a blocker. There is this Final criterion, which is quite clear: "The installer must be able to use all supported local and remote package and installer sources." https://fedoraproject.org/wiki/Fedora_33_Final_Release_Criteria#Package_and_installer_sources There is also this Basic criterion: "When using a release-blocking dedicated installer image, the installer must be able to use either HTTP or FTP repositories (or both) as package sources." https://fedoraproject.org/wiki/Basic_Release_Criteria#Remote_package_sources which is also repeated in Beta: https://fedoraproject.org/wiki/Fedora_33_Beta_Release_Criteria#Remote_package_sources This falls under HTTP(S), but it's not clear whether all repo types (plain URL, mirrorlist, metalink) are covered under it. Two questions: 1. Can you add non-metalink URLs successfully? 2. Can you add metalink URLs using a kickstart instead of the GUI? Knowing the answers to these would help my vote on Beta blocker status. (Final seems straightforward) Fixed in a pull request: https://github.com/rhinstaller/anaconda/pull/2857 we don't have the votes to accept as a Beta blocker yet, but we *do* have the votes in the ticket - https://pagure.io/fedora-qa/blocker-review/issue/94 - to accept as a Beta FE at least, so marking accepted so anaconda folks can pull this in for a build/update. (In reply to Ben Cotton from comment #9) > 1. Can you add non-metalink URLs successfully? A direct repository URL can be added successfully, yes. According to the PR, mirrorlists are probably broken as well. FEDORA-2020-e1d834c1ef has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2020-e1d834c1ef Kamil: no, mirrorlists work. At least according to openQA, which tests them. Does seem odd, though. FEDORA-2020-e1d834c1ef has been pushed to the Fedora 33 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-e1d834c1ef` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-e1d834c1ef See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. You can use https://www.happyassassin.net/temp/00669088-FEDORA-2020-e1d834c1ef-netinst-x86_64.iso to test the fix for this. It's the netinst ISO which openQA built to test the update. (In reply to Adam Williamson from comment #16) > You can use https://www.happyassassin.net/temp/00669088-FEDORA-2020-e1d834c1ef-netinst-x86_64.iso to test the fix for this. 404 Not Found D'oh, sorry, I forgot the bit where I actually copy it to the web server...:) It's there now. The ISO from comment 16 works fine, I can add a metalink repository and it gets used. Discussed at 2020-09-21 blocker review meeting: https://meetbot-raw.fedoraproject.org/fedora-blocker-review/2020-09-21/f33-blocker-review.2020-09-21-16.00.html . Rejected as a Beta blocker as there isn't any clear Basic or Beta criterion here. Accepted as a Final blocker as a clear violation of "The installer must be able to use all supported local and remote package and installer sources." FEDORA-2020-e1d834c1ef has been pushed to the Fedora 33 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2020-384ff75a01 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2020-384ff75a01 FEDORA-2020-384ff75a01 has been pushed to the Fedora 33 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-384ff75a01` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-384ff75a01 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2020-384ff75a01 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2020-384ff75a01 FEDORA-2020-384ff75a01 has been pushed to the Fedora 33 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-384ff75a01` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-384ff75a01 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2020-384ff75a01 has been pushed to the Fedora 33 stable repository. If problem still persists, please make note of it in this bug report. |