Bug 1451040

Summary: Failing to build live CD because --mirrorlist is unable to parse metalink
Product: [Fedora] Fedora Reporter: Benjamin Berg <bberg>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 26CC: anaconda-maint-list, g.kaviyarasu, jonathan, mkolman, sbueno, vanmeeuwen+fedora, vponcova
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-05-15 16:08:14 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:

Description Benjamin Berg 2017-05-15 15:51:38 UTC 
I created a simple script to build a live image inside mock. When running it in a Fedora 25 mock environment this works fine (building a Fedora 25 image). The same thing running against Fedora 26 (building a 26 image) is failing however because the metalink URLs are not parsed correctly.

It seems that in both cases the generated kickstart files look almost identical, i.e. a repo defined like:
> repo --name="fedora" --mirrorlist=http://mirrors.fedoraproject.org/metalink?repo=fedora-$releasever&arch=$basearch

This works fine on Fedora 25 but for Fedora 26 the installer interprets the metalink file as mirrorlist and uses the lines of the XML document to build URLs. Simply replacing "metalink" with "mirrorlist" in the kickstart file works around the issue.


In the mock environment I installed the following packages:
 * lorax-lmc-novirt
 * git (to grab https://pagure.io/fedora-kickstarts.git)
 * vim-minimal
 * pykickstart
Comment 1 Samantha N. Bueno 2017-05-15 16:08:14 UTC 
Looks like the base issue is the same as 1450129.

*** This bug has been marked as a duplicate of bug 1450129 ***