Bug 955724 - kickstart option "repo --name=fedora" does not find and use fedora repo
Summary: kickstart option "repo --name=fedora" does not find and use fedora repo
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 18
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-04-23 16:04 UTC by Edgar Hoch
Modified: 2013-05-22 03:17 UTC (History)
7 users (show)

Fixed In Version: anaconda-19.24-1.fc19
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-05-22 03:17:48 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Edgar Hoch 2013-04-23 16:04:07 UTC
Description of problem:
I use in my kickstart file the following options:

nfs --server=myserver.example.com --dir=/fs/boot_dir/Fedora/18/x86_64
repo --name=fedora
repo --name=updates

With Fedora 16 it has worked as expected. It uses the repos fedora and updates to get packages and updates that are not on the dvd (copied to disk, used by nfs).

With Fedora 18 anaconda doesn't find the repo "fedora".
I found the following error messages in
/var/log/anaconda/anaconda.packaging.log :

07:04:03,039 DEBUG packaging: adding yum repo fedora with baseurl  and mirrorlist None
07:04:03,041 ERR packaging: repo fedora setup failed: Cannot find a valid baseurl for repo: fedora
07:04:03,041 DEBUG packaging: removing repo fedora


See also https://fedoraproject.org/wiki/Anaconda/Kickstart#repo :

"If you want to enable one of the repos in /etc/anaconda.repos.d that is disabled by default (like "updates"), you should use --name=<repoid> but none of the other options. anaconda will look for a repo by this name automatically."


Version-Release number of selected component (if applicable):
New Fedora 18 kickstart installation.
kernel-3.8.8-202.fc18.x86_64
anaconda-yum-plugins-1.0-8.fc18.noarch
anaconda-18.37.11-1.fc18.x86_64


How reproducible:
Always.

Steps to Reproduce:
1. Create a kickstart file containing something like

nfs --server=myserver.example.com --dir=/path/to/Fedora/18/x86_64
repo --name=fedora
repo --name=updates

2. Kickstart
3. Search for fedora in /var/log/anaconda/anaconda.packaging.log

Actual results:
fedora repo is not found.

Expected results:
fedora repo is used while kickstart installation.

Additional info:

Comment 1 Edgar Hoch 2013-04-23 17:20:53 UTC
I tried to use more "repo" kickstart options and changed the order.
For example, when I use

nfs --server=myserver.example.com --dir=/path/to/Fedora/18/x86_64
repo --name=notfound
repo --name=fedora
repo --name=updates

then the repo "fedora" is found, but the repo "updates" is not found.
(Of course, "notfound" is not found.)

I have made more tests, and it seems, that only the second "repo" option with no mirrorlist is found. I there is a first repo with mirrorlist, then this is also found. In the following example the repos anaconda,fedorakickstart,updates are found.

nfs --server=myserver.example.com --dir=/path/to/Fedora/18/x86_64
repo --name=fedorakickstart --mirrorlist=https://mirrors.fedoraproject.org/metalink?repo=fedora-18&arch=x86_64 --cost=10
repo --name=notfound
repo --name=updates
repo --name=fedora
repo --name=fedora2kickstart --mirrorlist=https://mirrors.fedoraproject.org/metalink?repo=fedora-18&arch=xi686 --cost=10

In the following example only the repos anaconda,fedora are found:

nfs --server=myserver.example.com --dir=/path/to/Fedora/18/x86_64
repo --name=notfound
repo --name=fedora
repo --name=updates
repo --name=fedora2kickstart --mirrorlist=https://mirrors.fedoraproject.org/metalink?repo=fedora-18&arch=xi686 --cost=10


So I redefine the problem:

Some "repo" options in kickstart file are not processed in the right way.
- In some cases the given name is not matched agains predefined repos like "fedora" and "updates"
- The correct processing depends on the order and position of the repo option.

Comment 2 Edgar Hoch 2013-04-24 03:59:51 UTC
The following part of kickstart options seems to works for me
(as a workaround, not instead of a fix):

nfs --server=myserver.example.com --dir=/path/to/Fedora/18/x86_64
repo --name=fedora-kickstart --mirrorlist=https://mirrors.fedoraproject.org/metalink?repo=fedora-18&arch=x86_64 --cost=10
repo --name=fedora
repo --name=updates

Then anaconda activates the repos anaconda,fedora-kickstart,updates .

After installation no repo "fedora-kickstart" exists.
The only disadvantage of this workaround is that with "yum list" some packages are listed as installed from repo @fedora-kickstart instead of @fedora .

Comment 3 Fedora Update System 2013-04-30 12:22:00 UTC
anaconda-19.23-1.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/anaconda-19.23-1.fc19

Comment 4 Fedora Update System 2013-04-30 20:00:43 UTC
Package anaconda-19.23-1.fc19:
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing anaconda-19.23-1.fc19'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-7049/anaconda-19.23-1.fc19
then log in and leave karma (feedback).

Comment 5 Fedora Update System 2013-05-03 21:05:05 UTC
anaconda-19.24-1.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/anaconda-19.24-1.fc19

Comment 6 ajs 2013-05-17 16:33:55 UTC
I can confirm that this is fixed in F19 Beta RC1

Comment 7 Fedora Update System 2013-05-22 03:17:48 UTC
anaconda-19.24-1.fc19, python-blivet-0.12-1.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.